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:32:02 2001 [thread overview]
Message-ID: <01071323314701.00707@localhost> (raw)
In-Reply-To: <20010713141434.H22931@cvs.gentoo.org>
On Friday 13 July 2001 23:14, you wrote:
> On Fri, Jul 13, 2001 at 11:12:17PM +0300, Dan Armak wrote:
> > > This is a good idea; any takers who want to work on a new version of
> > > the xfree ebuild?
> > >
> > > Best Regards,
> >
> > BTW: we might finally incorporate the nvidia drivers as well.
>
> Well, I don't want to add the nvidia drivers to the xfree ebuild, since
> they don't require the xfree sources to build. We should only add things
> to the main xfree build if they really need the xfree sources to compile;
> otherwise, it's more efficient to add them as a separate package.
Of course. But then, do these ati/savage drivers really need the X sources?
(i.e. not just the installable headers). In any case, if we have USE flags
for ATI/savage as suggested in the orig. post, we might as well have one for
nvidia.
BTW: what's the policy for creating new USE keywords? There's an awful lot
already, and it seems we might create one for every second package. There are
always package interdependencies. LyX can make use of some 20 packages, but
that's no reason for having a USE keyword for each of them! Maybe we should
have a setting "USE_ALL" that would always build all possible dependencies of
which a package can make use. This could be useful for testing etc.
Dan Armak
next prev parent reply other threads:[~2001-07-13 20:31 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 [this message]
2001-07-13 14:49 ` Ben Lutgens
2001-07-13 14:56 ` Dan Armak
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=01071323314701.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