On 09/11/10 12:41, Peter Bex wrote:
Well, go ahead and add it :)
(chicken-install already ignores unknown meta declarations)
I am! I'm just suggesting it in case anybody else does the same thing,
so they don't come up with a *different* tag ;-)
ABS
--
Alaric Snell-Pym
http://www.snell-pym.o
I've been making slow progress refreshing the Arch Linux package scripts
for installing eggs.
I've accumulated notes about metadata and installation bugs
in various eggs, which I will pass on soon.
I had written earlier about my puzzlement re the difference between
CHICKEN_INSTALL_PREFIX=/alt
On Sun, Sep 12, 2010 at 10:03:17AM -0400, Jim Pryor wrote:
> I've been making slow progress refreshing the Arch Linux package scripts
> for installing eggs.
>
> I've accumulated notes about metadata and installation bugs
> in various eggs, which I will pass on soon.
Here are some of the metadata
From: Alaric Snell-Pym
Subject: [Chicken-users] Autoloading optional dependencies
Date: Sat, 11 Sep 2010 10:03:56 +0100
>
> Hi there folks
>
> I've noticed that the autoload egg goes partway towards solving
> Ugarit's
> "depends on EVERY hash, compression, and encryption egg" problem.
>
> For
From: Jim Pryor
Subject: [Chicken-users] More on Packaging eggs
Date: Sun, 12 Sep 2010 10:03:17 -0400
> (Do install-{extension,program,script} turn to NOPs when
> chicken-install is invoked with the -n option?)
Exactly.
cheers,
felix
___
Chicken-use
On 09/12/10 15:49, Felix wrote:
But that wouldn't work inside modules, because you would have to
have access to the import library, right?
If there's macros involved, yes - but then autoloading macros makes no
sense as they're loaded at compile time anyway. When you set up an
autoload, no comp
Hi all,
CHICKEN 4.6.0 has been released and is available at the following URL:
http://code.call-cc.org/releases/4.6.0/chicken-4.6.0.tar.gz
The changes in this release are described in the NEWS file available here:
http://code.call-cc.org/releases/4.6.0/NEWS
-Ivan
__
From: Alaric Snell-Pym
Subject: Re: [Chicken-users] Autoloading optional dependencies
Date: Sun, 12 Sep 2010 21:11:45 +0100
> On 09/12/10 15:49, Felix wrote:
>
>> But that wouldn't work inside modules, because you would have to
>> have access to the import library, right?
>
> If there's macros
