On Thursday 11 August 2005 07:02 am, Jason Stubbs wrote:
> On Thursday 11 August 2005 09:04, Mike Frysinger wrote:
> > On Wednesday 10 August 2005 07:56 pm, Jason Stubbs wrote:
> > > I was referring to compiler version. Portage FEATURES are not a
> > > guaranteed part of an ebuild's "shell". Let me put it another way,
> > > should ebuilds handle NOCOLOR as well?
> >
> > no, but why should NOCOLOR affect how a package is built/installed ? the
> > point here is that we dont really care whether it's FEATURES or USE or
> > what, as long as we have the ability to control DEPEND/SRC_URI/behavior
> > in an ebuild depending on whether the user wants tests/manpages/etc...
>
> With noman and the like, how's the following for a solution? A lot of the
> ebuild functions contained within portage will be moving into the tree once
> signing is in. What about adding {pre,post}_src_{compile,install,...} hooks
> into portage that will live in the tree that USE="man" support can be
> implemented in globally? For those packages that have a specific interest,
> the USE flag will be available. Everything should be happy on the ebuild
> side of things. (On the U/I side of things, stuff can be done to cut down
> the noise.)
so you're saying that the default ebuild.sh functions are going to be moving
into the tree to a place which will be auto-sourced before the ebuild and its
eclasses ?
-mike
--
gentoo-dev@gentoo.org mailing list
