Re: [PATCH] recover CHICKEN_INSTALL_PREFIX

[felix . winkelmann]

> 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.

> 
> I checked, but if I call chicken-uninstall with CHICKEN_EGG_PREFIX,
> it uninstalls (or attempts to uninstall) the egg in the "standard"
> location.  That means chicken-uninstall doesn't work if you're using
> CHICKEN_EGG_PREFIX.

You probably mean CHICKEN_INSTALL_PREFIX. But the patch had a bug: the
location for .egg-info files needs to be the main repository, only
the place of the target files have to be changed and stored in the
..egg-info. The attached new variant of the patch fixes that so that
-status and -uninstall work regardless of the prefix setting during
-install.
> 
> So why not simply replace the definition of destination-repository
> with the new code?

Because we have two locations: the normal repository where meta-data
is stored and the location where artifacts are stored.


felix

0001-Allow-overriding-general-installation-prefix-in-chic.patch
Description: Text document