On Sun, 2005-11-27 at 16:28 +0000, Mike Frysinger wrote:
> On Sun, Nov 27, 2005 at 11:12:32AM -0500, Ned Ludd wrote:
> > On Mon, 2005-11-28 at 00:48 +0900, Jason Stubbs wrote:
> > > On Monday 28 November 2005 00:05, Jason Stubbs wrote:
> > > > 3) FEATURES="noman" is dropped in favour of USE="man" or USE="manpages"
> > > >
> > > > In light of the above requirements and the fact that dyn_* will likely 
> > > > be
> > > > moved into the tree down the track, #3 seems to be the best in my mind.
> > > > Similarly, it would solve the previously discussed problems related to
> > > > FEATURES="test".
> 
> this seems like the best idea imo too ...
> 
> > > I'd be very interested in people's thoughts on this. The more I think 
> > > about 
> > > it, the more I think it's the most appropriate solution. Nothing in 
> > > FEATURES="noman nodoc noinfo test" affects portage whatsoever other than 
> > > "noinfo" which (only recently) prevents emerge from regenerating info 
> > > indexes. That one could be handled by a hook (although not yet available) 
> > > and 
> > > the rest could easily be switched to USE flags.
> > 
> > USE=(man|info|doc) wont quite work.
> > While they could have an advantage that you can use them to control 
> > depend strings the doc use flag has already been heavily used for other 
> > things which everybody surely wont want.
> 
> i dont see what USE=doc has to do with this ?  doc should never be used
> to control manpages in ebuilds now ...

The 3 no* features in question. Removing just one would be silly. So 
they either all should go or all stay. If noman were to become USE=man 
then logic would say that nodoc would become USE=doc and noinfo would 
become USE=info. Unless we want to call them 
USE=(docpages|manpages|infopages) all respectively then it wont matter 
so much. But then USE=-* emerge foo would all of the sudden make USE=-* 
kinda suck for users who just want to escape the normal default-linux 
USE flag bloat.

-- 
Ned Ludd <[EMAIL PROTECTED]>
Gentoo Linux

-- 
gentoo-dev@gentoo.org mailing list

Reply via email to