From: Dan Armak <ermak@netvision.net.il>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] feature request for X ebuild
Date: Fri Jul 13 14:56:02 2001 [thread overview]
Message-ID: <01071323550704.00707@localhost> (raw)
In-Reply-To: <20010713154742.A555@minime.sistina.com>
On Friday 13 July 2001 23:47, you wrote:
> On Fri, Jul 13, 2001 at 11:31:47PM +0300, Dan Armak wrote:
> >have a setting "USE_ALL" that would always build all possible dependencies
> > of
>
> God help us! NO! what a monstrous thing to undertake! Can you imagine
> making a kernel compile with all those conflicting drivers and patches!!!
> It'd be a nightmare. Or building some app that can use GTK or QT compile
> with both (not sure if there are any, that would be stupid) but you get
> my point.
OK, OK! But I still think we need to organize our USE flags.
Dan Armak
next prev parent reply other threads:[~2001-07-13 20:55 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-07-13 13:51 [gentoo-dev] feature request for X ebuild Taras Glek
2001-07-13 14:08 ` Daniel Robbins
2001-07-13 14:13 ` Dan Armak
2001-07-13 14:15 ` Daniel Robbins
2001-07-13 14:32 ` Dan Armak
2001-07-13 14:49 ` Ben Lutgens
2001-07-13 14:56 ` Dan Armak [this message]
2001-07-13 14:53 ` Daniel Robbins
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=01071323550704.00707@localhost \
--to=ermak@netvision.net.il \
--cc=gentoo-dev@cvs.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