Re: Best way to track and isolate project dependencies?

[alice maz]

there's nothing stopping someone from maintaining an egg file for something 
they don't intend to package, and just building it with chicken-install 
-no-install. could also use a custom build script to set the egg env vars too. 
personally I just manage this stuff with my own build system tho, and I think 
most people just use makefiles

-alice

On Thu, Sep 10, 2020, at 11:31, Lukas Böger wrote:
> You can set two environment variables to control the installation 
> directory as well as the module search path. Example:
> 
> export CHICKEN_INSTALL_REPOSITORY="/path/to/project/eggs"
> export CHICKEN_REPOSITORY_PATH="/usr/lib/chicken/11/:/path/to/project/eggs"
> 
> If you use bash or comparable as a shell, you could save those settings 
> in a project-specific file and source them.
> 
> If you install an egg with some dependencies, all those will be pulled 
> in the above directory.
> 
> As far as I know, there is no streamlined way of tracking dependencies 
> of a project, though.
> 
> Lukas
> 
>