From: Alan McKinnon <alan@linuxholdings.co.za>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: xorg INPUT and VIDEO USE flags
Date: Mon, 16 Oct 2006 18:48:12 +0200 [thread overview]
Message-ID: <200610161848.12977.alan@linuxholdings.co.za> (raw)
In-Reply-To: <358eca8f0610160910v40406e75rf585b932eb16ff9a@mail.gmail.com>
On Monday 16 October 2006 18:10, Mick wrote:
> Thanks Alan, but the question I meant to ask is: why only the
> xorg-server takes account of these flags, while the xorg-x11 doesn't?
xorg-x11 is a meta package. It's purpose is to merge various x11
packages as dependencies and it doesn't do any merging on it's own.
Looking into the ebuilds, xorg-x11 only mentions VIDEO_CARDS and
INPUT_DEVICES once in pkg_postinst() in an einfo saying you should now
set these variables (presumably so that xorg-server can do the right
thing when it's merged).
The xorg-server-1.1.1-r1 ebuild contains stuff like this:
PDEPEND="
xorg? (
input_devices_mouse? ( >=x11-drivers/xf86-input-mouse-1.1.0 )
video_cards_radeon? ( >=x11-drivers/xf86-video-ati-6.6.0 )
So the variable is only used by the ebuild that actually does the
merging.
Your 'emerge xorg-x11' lists a bunch of USE flags in the output, but
they are all disabled and appended with %, meaning they are new flags
being used for the first time. Do the merge then try it again, you
should find they are not listed the second time. Portage and the output
it generates is in a state of flux recently with several updates in
parid succession. It's sometimes a bit hard to keep up with the changes
and remember what it's supposed to do today :-)
But the output you are getting is correct per my current understanding
of portage
alan
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-10-16 16:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-16 14:56 [gentoo-user] xorg INPUT and VIDEO USE flags Mick
2006-10-16 15:49 ` Alan McKinnon
2006-10-16 16:10 ` [gentoo-user] " Mick
2006-10-16 16:48 ` Alan McKinnon [this message]
2006-10-16 19:58 ` Mick
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=200610161848.12977.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