[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Chicken-users] srfi-128 - almost

From: Jörg F . Wittenberger
Subject: Re: [Chicken-users] srfi-128 - almost
Date: 20 Aug 2018 19:33:24 +0200

Thanks Mario,

at the end of the day your suggestion will solve the development time considerations I have. Except for the "check the download process" part.

Though actually rolling those out over a test network looks like a bookkeeping hell.

Brings me to a downside of C5 I'm seeing so far: I now need to tell it where it should maintain its cache. I wonder how I could maintain a consistent overwrite for setup.defaults for all the receipes in a yocto build. Plus where goes this new cache?



On Aug 19 2018, Mario Domenech Goulart wrote:

On Sat, 18 Aug 2018 15:57:52 +0300 megane <address@hidden> wrote:

Hi Jörg,

Jörg F. Wittenberger <address@hidden> writes:

Brings back the question: how would I tell chicken to temporarily consult other locations for egg distributions? E.g. I'd like to use chicken-install in a fresh location outside the source directory of the egg to check that the whole download picks the correct files and all of them. Or maybe I just want to install an egg I deem not good enough to release.

Maybe you're looking for a custom entry in share/chicken/setup.defaults.
Maybe something like:

(server (location "/path/to/my/eggs") (transport local))

Actually just

 $ echo "(location $EGGS_DIR)" >> $PREFIX/share/chicken/setup.defaults

should be enough.

Where EGGS_DIR is the directory where directories containing egg source
code can be found and $PREFIX is the CHICKEN installation prefix (what
you provided as argument to PREFIX when compiling CHICKEN).

If the egg you try to install (or its dependencies) cannot be found in
$EGGS_DIR, chicken-install will fall back to the `server' configuration
in setup.defaults (which defaults to the primary egg server).

All the best.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]