Re: [PATCH] recover CHICKEN_INSTALL_PREFIX

[felix . winkelmann]

> On Wed, Aug 16, 2023 at 05:25:45PM +0200, felix.winkelmann@bevuta.com wrote:
> > > Why are install-path and repo-path in chicken-install.scm still using
> > > destination-repository instead of effective-destination-repository?
> > > Those are the only places that still use it, aside from one in
> > > chicken-status and chicken-uninstall.
> > 
> > The prefix variable is only used for designating where the build
> > artifacts are to be stored, not where extensions are located or
> > where .egg-info files are to be stored. It also makes sense to set
> > CHICKEN_REPOSITORY_PATH in addition to CHICKEN_INSTALL_PREFIX when
> > dependency extensions installed and used during the build of another
> > extension are needed to be located. This _is_ confusing, no doubt
> > about that, but we need a way to override install target locations,
> > especially for include-files and binaries and has been requested 
> > several times by users, IIRC.
> 
> It's extremely confusing and hard to use correctly, but it seems to work
> as intended, so I've pushed the patch.
> 

Thanks. As I said, I agree completely that it is not a shining example of
software design. The problem is that there is a certain build/install/deployment
situation that we can't cover without such a device (unless using horrible 
workarounds).


felix