Bug 209855 – dev-scheme/chicken: default egg repository path and chicken's .exports path differ.

• Product: Gentoo Linux
• Status: RESOLVED NEEDINFO

[Description Leonardo Valeri Manera 2008-02-12 15:04:43 UTC]

Chicken's .exports files are installed in /usr/share/chicken, but optional eggs are still installed into /usr/lib/chicken/3 by chicken-setup...

Extensions shouldn't really go in /usr/lib when the base package's export files go into /usr/share, surely?

Can you make these 2 agree with each other, or at least make sense?

Eggs could go in /usr/share/chicken/eggs/3, for example, or the .exports could go in /usr/lib/chicken, with the eggs in /usr/lib/chicken/3 as per default.

Its possible to set the egg path with CHICKEN_REPOSITORY, but the main package itself really ought to set sane defaults for system-wide installation itself w/out using env_vars :)

Reproducible: Always

Steps to Reproduce:

[Comment 1 Jakub Moc (RETIRED) 2008-02-12 18:25:09 UTC]

Well, maybe you could ask your question somewhere else in the first place; thanks.

[Comment 2 Leonardo Valeri Manera 2008-02-12 21:51:14 UTC]

Thanks yourself, I was told by hkBst to open this very bug. Blame him :)

[Comment 3 Jakub Moc (RETIRED) 2008-02-12 21:57:26 UTC]

Yeah great; thanks for information.

[Comment 4 Marijn Schouten (RETIRED) 2008-02-13 11:22:16 UTC]

Leonardo, consistency is nice of course, but didn't you also mention some failure this is causing?

[Comment 5 Leonardo Valeri Manera 2008-03-04 17:29:56 UTC]

Yes, I did get an egg build error on a few occasions which _seemed_ to be caused by the fact that we leave the hardcoded repository variable to /usr/lib/chicken/3 but install .export files in /usr/share/chicken, and disappeared once I defined CHICKEN_REPOSITORY=/usr/share/chicken.

I'm not sure what's causing this however, as the we're not doing it any different from the binary builds found on the chicken website.