From: "Richard Fish" <bigfish@asmallpond.org>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] xorg-x11, $VIDEO_CARDS & binary packages
Date: Thu, 20 Jul 2006 00:40:58 -0700 [thread overview]
Message-ID: <7573e9640607200040s7127d16bxf8e275bb19be9107@mail.gmail.com> (raw)
In-Reply-To: <200607200744.21927.alexander.puchmayr@linznet.at>
On 7/19/06, Alexander Puchmayr <alexander.puchmayr@linznet.at> wrote:
> > I'd recommend you emerge --nodeps xorg-x11 in order to change its
> > USEflags to the ones you want (no compilation necessary), and then
> > emerge -k to pull in the binary packages depended on by its new flags,
> > which will save you the compiling time.
> >
> > HTH.
>
> Nope, doesn't work. Same problem. I emerged with --nodeps the xorg-x11
> package, with exactly the video-cards I want. Then I've tried the -k as you
> suggested, and still *ALL* other video-drivers are shown in the list, and
> VIDEO_CARDS did not show the same content as without -k.
Do you have buildpkg in FEATURES? If not, you might need to do:
emerge --nodeps xorg-x11
quickpkg xorg-x11
emerge -k xorg-x11
If you don't have buildpkg in FEATURES, and don't do the quickpkg
step, then the second emerge will again look at your existing binary
package of xorg-x11, and use the settings from that.
HTH,
-Richard
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-07-20 7:51 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-19 4:51 [gentoo-user] xorg-x11, $VIDEO_CARDS & binary packages Alexander Puchmayr
2006-07-19 6:44 ` Richard Fish
2006-07-19 18:20 ` Richard Fish
2006-07-20 4:29 ` Alexander Puchmayr
2006-07-20 4:56 ` Ryan Tandy
2006-07-20 5:44 ` Alexander Puchmayr
2006-07-20 7:40 ` Richard Fish [this message]
[not found] ` <200607202019.25875.alexander.puchmayr@linznet.at>
2006-07-20 18:37 ` Richard Fish
2006-07-20 19:25 ` Richard Fish
2006-07-20 15:54 ` Ryan Tandy
2006-07-20 18:25 ` Alexander Puchmayr
2006-07-20 18:40 ` Daniel da Veiga
2006-07-20 20:10 ` Hans-Werner Hilse
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=7573e9640607200040s7127d16bxf8e275bb19be9107@mail.gmail.com \
--to=bigfish@asmallpond.org \
--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