Re: [gentoo-dev] Customize a ebuild before compiling

[Hendrik Visage]

On Sat, Aug 11, 2001 at 01:28:22PM -0500, tadpol@××××××.org wrote:
> On Sat, Aug 11, 2001 at 06:52:22PM +0200, Hendrik Visage wrote:
> > On Sat, Aug 11, 2001 at 01:45:28AM +0200, Karl Trygve Kalleberg wrote:
> > > One of the decisions to make is whether we should expose the underlying
> > > configuration mechanism for the package, say by having a process much like
> [snip]
> > > The current philosophy of portage (and consequently ebuild) has been KISS.
> > > The Gentoo developers have opted for the easiest route,
> > > implementation-wise.
> >
> > Which do take away my reasons  for needing to build
> > from source :(
>
>
> There will always be packages that are too `weird' to be handled by any
> system we come up with.
>
> At a certain point, the extra complexity needed for this kind of stuff is
> not worth the time.
>
> /usr/local/(bin|sbin|share|doc|*) exists for a reason.  If you have
> packages that require that level of customization, it is probably beyond
> what a package system should do.

Which breaks the idea of a packaging system :(

Even worse, I'd like to build a special version of gtk (thumb sucking),
and wish everything from then on to make use of this version.

If I'm going to install in /usr/local, then the portage system isn't
going to pick it up (easily I guess) that I've installed version x.y.z_patched
and that it don't need to build x.y.z and to configure/compile against /usr/local
instead of the "old" /usr version...

How can we still link in with the dependency & packaging system, 
without breaking portage etc. and not making use of ebuild???

> This all of course is my own personal opinion,

Mine too ;)

-- 
------------------------
Hendrik Visage
hvisage@×××××××××××.za