On 2018-09-27 21:38, felix.winkelm...@bevuta.com wrote:
> Opinions?
I'm for it, yeah.
In 5.0 people can make do with custom-build, but having cond-expand
available would be nice for simple cases.
Evan
___
Chicken-hackers mailing list
On 2018-09-28 10:38, felix.winkelm...@bevuta.com wrote:
> A trivial change, fixing an unnecessary test reported by the
> scrutinizer during build.
This hctap has been applied, thanks!
Evan
___
Chicken-hackers mailing list
Chicken-hackers@nongnu.org
> The problem with old versions of chicken-install would be they don't
> understand those new forms. But for those I guess you'd just pin
> the version of the egg to an older one.
With cond-expand in egg files, you can always do a
(cond-expand (chicken-5.x ...) (else ...))
felix
On Fri, Sep 28, 2018 at 08:28:21PM +0200, Jörg F. Wittenberger wrote:
> One more idea: How about an entry indicating the version of the egg file
> syntax?
>
> Having something to cond-expand is nice. But it might be hard to settle with
> a final version without unduly delaying CHICKEN 5.
>
>
Hi!
I don't have to salute, do I? ;-)
On Sep 27 2018, felix.winkelm...@bevuta.com wrote:
Hi!
I wonder: there is no way to conditionally set options, configure egg
building, etc. I think it would be handy to have a "cond-expand" form
that can be used inside ..egg files customize the egg
Hi!
A trivial change, fixing an unnecessary test reported by the
scrutinizer during build.
felix
From 57171d0d9dfe8dafcd52a84954081e367319fa2b Mon Sep 17 00:00:00 2001
From: felix
Date: Thu, 27 Sep 2018 22:07:22 +0200
Subject: [PATCH] drop unnecessary test
---
lolevel.scm | 2 +-
1 file
felix.winkelm...@bevuta.com wrote:
> I wonder: there is no way to conditionally set options, configure egg
> building,
> etc. I think it would be handy to have a "cond-expand" form that can be used
> inside
> ..egg files customize the egg build/installation depending on platform.
> […]
>
