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:
Well, maybe you could ask your question somewhere else in the first place; thanks.
Thanks yourself, I was told by hkBst to open this very bug. Blame him :)
Yeah great; thanks for information.
Leonardo, consistency is nice of course, but didn't you also mention some failure this is causing?
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.
