On Thursday 11 August 2005 09:04, Mike Frysinger wrote: > On Wednesday 10 August 2005 07:56 pm, Jason Stubbs wrote: > > On Thursday 11 August 2005 00:39, Mike Frysinger wrote: > > > On Wednesday 10 August 2005 11:24 am, Jason Stubbs wrote: > > > > On Wednesday 10 August 2005 22:19, Ciaran McCreesh wrote: > > > > > On Wed, 10 Aug 2005 09:10:39 -0400 Michael Cummings > > > > > > > > > > <[EMAIL PROTECTED]> wrote: > > > > > | (not directed at dsd in particular, just the last one in my > > > > > | inbox to reply :) That's great and all that its in features for > > > > > | the installation, but what about packages with optional > > > > > | dependencies based on doc and man? > > > > > > > > > > Join in the quest to get FEATURES added to the expand list! Bug > > > > > #82513. > > > > > > > > How much do you like C code that has > > > > #ifdef's for the compiler being used? It's the same thing. > > > > > > i'll take > > > #ifdef __x86_64__ > > > over > > > use amd64 > > > any day > > > > 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...
As well as having the option presented to the user in a unified way. ;)
Really, something along the lines of Carsten's base.eclass suggestion sounds
best to me. The fact that ebuilds are find what are currently portage
FEATUREs to be interesting implies in my mind that they either shouldn't be
FEATUREs (noman, noinfo) or that the relation to ebuilds should be
investigated further and dealt with appropriately (test, debug).
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.)
--
Jason Stubbs
pgpPOnnZ2ACgo.pgp
Description: PGP signature
