Re: [Chicken-hackers] TinyCLOS 'examples' install path?

[Ivan Raikov]

  Good point, after I wrote you my previous email, I realized the
various ways to set installation paths can be confusing, so I started
updating the chicken-setup man page. 

  Right now, CHICKEN_REPOSITORY is not checked in chicken-setup,
although the man page claims otherwise. I am going to put this back,
so we are consistent with the documentation.

  When you specify -destdir foo, the repository path is set to
destdir/lib/chicken. The "lib/chicken" string is hardcoded in the
chicken-setup source code, and I don't immediately see a good reason
to do so. I will look around some more, but I think I will change
that, and maybe add a separate -dest-prefix option, which will behave
like the current -destdir. In a separate email, I will write up the
algorithm for choosing installation paths, and if nobody disagrees
with it, I will update chicken-setup to make sure it respects all its
environment variables and installation path options.

  -Ivan


"Leonardo Valeri Manera" <address@hidden> writes:

>
> If DESTDIR is what you give after -R, yeah.
>
> I'm finding the whole paths thing for chicken-setup a little
> confusing, to be quite honest, especially these 2 cases:
>
> (assume you're in the dir with the unpacked tinyclos egg)
>
> chicken-setup -R ./install -P ./binaries =>
> egg files go into install/, examples go into CHICKEN_REPOSITORY (which
> should be overriden by -R, but isn't)
>
> chicken-setup -R ./install -P ./binaries -destdir foo =>
> egg files go into foo/lib/chicken/install/ , examples into
> foo/examples/ (where did lib/chicken come from? what happened to my
> CHICKEN_REPOSITORY=/usr/share/chicken variable now? It was'nt being
> overridden by -R before...)
>
> I feel like I'm an episode of the twilight zone.
>
> Cheers,
> Leo