This looks pretty close.
Where do I learn what I can put into setup.defaults? Looks like it could do
the job I want.
What I don't want: a local copy of the to-be-installed egg to begin with.
What I want: chicken-install installing eggs almost like normal. For eggs
being overwritten however, I'd want it to go through the complete download
process, just using the location from the other release-info.
Great if a hand full of overwrites could sit in a single file like
setup.defaults.
On Aug 18 2018, megane wrote:
Hi Jörg,
Jörg F. Wittenberger <[email protected]> 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))
_______________________________________________
Chicken-users mailing list
[email protected]
https://lists.nongnu.org/mailman/listinfo/chicken-users
