From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] manpages that requires dependencies
Date: Sun, 27 Nov 2005 16:28:14 +0000 [thread overview]
Message-ID: <20051127162814.GA3272@toucan.gentoo.org> (raw)
In-Reply-To: <1133107952.21175.467.camel@localhost>
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 ...
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-27 16:30 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-24 23:49 [gentoo-dev] manpages that requires dependencies Diego 'Flameeyes' Pettenò
2005-11-24 23:58 ` Ciaran McCreesh
2005-11-25 0:03 ` Diego 'Flameeyes' Pettenò
2005-11-25 7:13 ` Re[2]: " Jakub Moc
2005-11-25 10:21 ` Alexandre Buisse
2005-11-25 10:46 ` Marius Mauch
2005-11-25 18:52 ` Mike Frysinger
2005-11-27 9:21 ` Kevin F. Quinn
2005-11-27 12:58 ` Ned Ludd
2005-11-27 13:09 ` Ned Ludd
2005-11-27 14:39 ` Jason Stubbs
2005-11-27 14:43 ` Re[2]: " Jakub Moc
2005-11-27 15:05 ` Jason Stubbs
2005-11-27 15:48 ` Jason Stubbs
2005-11-27 16:12 ` Ned Ludd
2005-11-27 16:28 ` Mike Frysinger [this message]
2005-11-27 16:48 ` Ned Ludd
2005-11-27 16:45 ` Diego 'Flameeyes' Pettenò
2005-11-27 14:47 ` Ned Ludd
2005-11-27 14:50 ` Diego 'Flameeyes' Pettenò
2005-11-27 15:01 ` Jason Stubbs
2005-11-27 15:43 ` Jason Stubbs
2005-11-27 16:49 ` Ciaran McCreesh
2005-11-27 17:30 ` Diego 'Flameeyes' Pettenò
2005-11-25 16:43 ` Michael Cummings
2005-11-25 19:27 ` Ciaran McCreesh
2005-11-25 16:52 ` Jason Stubbs
2005-11-25 19:27 ` [gentoo-dev] " Duncan
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20051127162814.GA3272@toucan.gentoo.org \
--to=vapier@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox