From: <burlingk@cv63.navy.mil>
To: <gentoo-user@lists.gentoo.org>
Subject: RE: [gentoo-user] Gentoo gets as bad SuSE: Circular dependencies [WAS: Thank you Gentoo devs]
Date: Mon, 21 May 2007 10:41:32 +0900 [thread overview]
Message-ID: <AA0639A1EB70AE409130258CE7BDC31806646AD9@messenger.cv63.navy.mil> (raw)
> Enrico Weigelt wrote:
> > The circular dependencies between Xserver and drivers do not come
> > from upstream. They're artificial. If we just want an simple-to-use
> > package which gets the Xserver *and* drivers based on useflags
> > (which IMHO is an good idea), it's quite trivial to do this by an
> > virtual/meta package. I've did it and it works good. You can get
> > it from my overlay via CVS:
> >
That is exactly what the xorg-x11 metapackage is designed to do.
If you don't add in a million USE flags that don't want to play nice,
then it should all compile (in theory). I say in theory, because
there are always things that can possibly get in the way. Bugs happen
on occasion. I am learning how to properly use USE flags myself. ^_^
--
gentoo-user@gentoo.org mailing list
next reply other threads:[~2007-05-21 1:45 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-21 1:41 burlingk [this message]
2007-05-30 15:59 ` [gentoo-user] Gentoo gets as bad SuSE: Circular dependencies [WAS: Thank you Gentoo devs] Enrico Weigelt
-- strict thread matches above, loose matches on Subject: below --
2007-05-18 10:26 burlingk
2007-05-18 4:56 burlingk
2007-05-18 10:01 ` Arturo 'Buanzo' Busleiman
2007-05-18 17:35 ` Enrico Weigelt
2007-05-18 22:48 ` Neil Walker
2007-05-04 10:37 [gentoo-user] xorg-7.2 and ati-drivers-8.32.5 Remy Blank
[not found] ` <f2d5ap$t7j$1@sea.gmane.org>
2007-05-15 20:56 ` [gentoo-user] Re: xorg-7.2 and ati-drivers-8.32.5 - Thank you Gentoo devs Francisco Rivas
2007-05-16 5:44 ` Johannes Skov Frandsen
2007-05-16 12:51 ` Francisco Rivas
2007-05-16 12:59 ` Remy Blank
2007-05-16 14:23 ` [gentoo-user] Gentoo gets as bad SuSE: Circular dependencies [WAS: Thank you Gentoo devs] Enrico Weigelt
2007-05-16 14:54 ` Neil Bothwick
2007-05-16 15:47 ` Enrico Weigelt
2007-05-16 16:17 ` Bo Ørsted Andresen
2007-05-17 15:46 ` Enrico Weigelt
2007-05-16 16:34 ` Rob Rutherford
2007-05-16 22:17 ` Neil Bothwick
2007-05-17 16:03 ` Enrico Weigelt
2007-05-17 17:21 ` Hemmann, Volker Armin
2007-05-18 10:29 ` Neil Bothwick
2007-05-19 3:00 ` Kent Fredric
2007-05-20 16:49 ` Enrico Weigelt
2007-05-20 17:55 ` Neil Bothwick
2007-05-20 23:32 ` Neil Walker
2007-05-21 1:15 ` kashani
2007-05-21 9:57 ` Andrey Gerasimenko
2007-05-21 10:44 ` Alan McKinnon
2007-05-21 11:15 ` Hans-Werner Hilse
2007-05-16 22:51 ` kashani
2007-05-16 23:08 ` Iain Buchanan
2007-05-17 23:19 ` Mark Shields
2007-05-16 15:51 ` Bo Ørsted Andresen
2007-05-16 22:04 ` Neil Bothwick
2007-05-16 22:40 ` Dale
2007-05-16 23:56 ` Neil Bothwick
2007-05-17 16:10 ` Enrico Weigelt
2007-05-17 17:20 ` Arturo 'Buanzo' Busleiman
2007-05-17 20:40 ` Boyd Stephen Smith Jr.
2007-05-17 18:21 ` Bo Ørsted Andresen
2007-05-16 21:31 ` Dan Farrell
2007-05-16 15:58 ` Francisco Rivas
2007-05-16 21:42 ` Jerry McBride
2007-05-16 21:57 ` Dale
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=AA0639A1EB70AE409130258CE7BDC31806646AD9@messenger.cv63.navy.mil \
--to=burlingk@cv63.navy.mil \
--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