> On Fri, Jul 21, 2023 at 03:54:41PM +0200, felix.winkelm...@bevuta.com wrote:
> > diff --git a/egg-compile.scm b/egg-compile.scm
> > index 99a94fe8..b14535da 100644
> > --- a/egg-compile.scm
> > +++ b/egg-compile.scm
> > @@ -412,7 +420,7 @@
> > (define (compile-common info walk)
> >
On Fri, Jul 21, 2023 at 03:54:41PM +0200, felix.winkelm...@bevuta.com wrote:
> diff --git a/egg-compile.scm b/egg-compile.scm
> index 99a94fe8..b14535da 100644
> --- a/egg-compile.scm
> +++ b/egg-compile.scm
> @@ -412,7 +420,7 @@
> (define (compile-common info walk)
>(case (car info)
Hi!
In complex build environments it is sometimes desirable to overriding
where "chicken-install" places programs, include- and data files, for
example when packaging. Currently it is possible to set
CHICKEN_INSTALL_REPOSITORY
to set where extensions are placed and in combination with
