From: Ned Ludd <solar@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] manpages that requires dependencies
Date: Sun, 27 Nov 2005 09:47:38 -0500 [thread overview]
Message-ID: <1133102858.5317.427.camel@localhost> (raw)
In-Reply-To: <200511272339.48235.jstubbs@gentoo.org>
On Sun, 2005-11-27 at 23:39 +0900, Jason Stubbs wrote:
> On Sunday 27 November 2005 22:09, Ned Ludd wrote:
> > On Sun, 2005-11-27 at 07:58 -0500, Ned Ludd wrote:
> > > On Fri, 2005-11-25 at 12:46 +0200, Marius Mauch wrote:
> > > > Except that no{man,info,doc} are on the to-die list anyway.
> > >
> > > They are very valuable features and quite easy to use without mucking
> > > with INSTALL_MASK. I'm against this change without some justification.
> >
> > further investigation shows that you can't simply get rid of these as
> > several core ebuilds use the feature to control the creation of
> > packages. A quick grep shows that several ebuilds do stuff like.
> > has noman FEATURES && do_stuff
> >
> > openssl/glibc/gcc/dhcp/boa/gdb to name a few that take advantage of the
> > no{man,info,doc} FEATURES= already.
>
> Core packages or not, they are all broken. When the requirement came up, the
> respective maintainers should have spoken up so that a proper solution could
> be found. When are the quick hacks going to stop? :|
Yeah I can also confirm that things are broken and hacks probably wont
stop till upstream for a given package starts making things like
nroff/groff optional vs forced. I really don't think we will see that
happening anytime soon.
--
Ned Ludd <solar@gentoo.org>
Gentoo Linux
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-27 14:50 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
2005-11-27 16:48 ` Ned Ludd
2005-11-27 16:45 ` Diego 'Flameeyes' Pettenò
2005-11-27 14:47 ` Ned Ludd [this message]
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=1133102858.5317.427.camel@localhost \
--to=solar@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