[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

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

From: Leonardo Valeri Manera
Subject: Re: [Chicken-hackers] TinyCLOS 'examples' install path?
Date: Sat, 8 Mar 2008 01:56:27 +0100

On 08/03/2008, Ivan Raikov <address@hidden> wrote:
>  I don't understand this -- what do you mean by some eggs "will
>  recompile again"? Can you provide an example? I want to make it very
>  easy to use chicken-setup for building binary packages for eggs, so
>  please do not hesitate to propose better semantics.

What I mean is that the egg build system does not support separate
compilation/installation actions, or at least not consistently.

With 3.0.0 chicken-setup it was (sometimes) possible to do this, with
the chicken-setup in trunk (which is much better, btw) this isnt
possible at all, from what I can tell.

Not that we at gentoo could make a use of such a feature if it existed because:

It also has no support for separate documentation installation paths.

I've reworked my eclass functions around trunk. Its working very
nicely, and you don't have to really bother with anything else on my
I compile and install in a temp dir in one action, where it would
normally be 2, then perform 'make install' equivalent actions to the
real sandbox install tree myself since I need to move the
documentation to /usr/share/doc.

Of course it would be better if I could make chicken-setup do that for
me, but that would probably be not worth the bother for you guys :)


reply via email to

[Prev in Thread] Current Thread [Next in Thread]