From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] X USE flag
Date: Mon, 30 Oct 2006 15:04:11 +0200 [thread overview]
Message-ID: <200610301504.11143.alan@linuxholdings.co.za> (raw)
In-Reply-To: <200610301302.16699.bo.andresen@zlin.dk>
On Monday 30 October 2006 14:02, Bo Ørsted Andresen wrote:
> > 1. What's causing these packages to have an X use flag at all?
> > 2. Why use such a flag at all? These are X11 packages, seems kinda
> > pointless to compile such a thing without X11 support...
>
> The x-modular.eclass now inherits the font.eclass ...
>
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/x-modular.ecla
>ss?r1=1.77&r2=1.78
> http://sources.gentoo.org/viewcvs.py/gentoo-x86/eclass/font.eclass?re
>v=1.21&view=markup
Ok, that's explains what's happening.
But now I have to recompile something on the order of 60 - 70 packages
with a new USE flag which is apparently not used anywhere (and is
simply an artifact of an inherit) (I checked some of the ebuilds, not
all, and none so far use that flag directly). I'll even predict money
that the new binaries are identical to the old ones.
Forgive my saying this, but that is a stupendous waste of my cpu cycles
and time. A better solution must exist - if this moves to arch
unchanged the gentoo user base will go ballistic
alan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-30 13:07 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-30 10:01 [gentoo-user] X USE flag Alan McKinnon
2006-10-30 12:02 ` Bo Ørsted Andresen
2006-10-30 13:04 ` Alan McKinnon [this message]
2006-10-30 13:21 ` Sascha Lucas
2006-10-30 16:22 ` Alan McKinnon
2006-10-30 18:38 ` Bo Ørsted Andresen
2006-10-30 18:48 ` Hans de Hartog
2006-10-30 19:41 ` Bo Ørsted Andresen
2006-10-31 7:13 ` Alan McKinnon
2006-10-31 8:30 ` Neil Bothwick
2006-11-01 17:57 ` Mark Shields
2006-11-01 20:23 ` Neil Bothwick
2006-11-01 20:36 ` Mark Shields
2006-11-01 22:12 ` Mrugesh Karnik
2006-10-30 19:46 ` Hans de Hartog
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=200610301504.11143.alan@linuxholdings.co.za \
--to=alan@linuxholdings.co.za \
--cc=gentoo-user@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