public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ben Skeggs <darktama@iinet.net.au>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Modular X update
Date: Sun, 11 Dec 2005 09:32:01 +1100	[thread overview]
Message-ID: <1134253921.29488.10.camel@araqiel.keine.ath.cx> (raw)
In-Reply-To: <439A0F51.9090707@gentoo.org>

Am Freitag, den 09.12.2005, 23:12 +0000 schrieb Donnie Berkholz:
> 2) Users with no X installed will pull in the virtual/x11 package 
> because there is no longer a default virtual.
A user in #gentoo-amd64 ran into issues with this that I reproduced in a
chroot.  On a new install, with no X installed you end up with messages
saying that virtual/x11 is blocking x11-base/xorg-x11-6.8.2-r6.

ie, Here's what happens when you attempt to merge aterm:
http://members.iinet.net.au/~darktama/aterm_merge.log
	
I'm not an expert, but the xorg-x11 ebuild has "!virtual/x11" in
DEPEND/RDEPEND, could this be why?

> I hope that covers pretty much everything right now.
When porting ebuilds to modular, how do we intend on handling the other
x11 virtuals in DEPEND/RDEPEND?  I'm assuming that we modify it so that
the modular dependencies depend directly on media-libs/mesa etc, and
leave virtual/opengl as the alternative?

Or should I just wait until the real virtual/{opengl,xft,glu,glut}
ebuilds exist before touching packages that need them?

> 
> Thanks for your patience,
> Donnie
Thanks for your work on this!
Ben.
-- 
gentoo-dev@gentoo.org mailing list



  parent reply	other threads:[~2005-12-10 22:34 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-12-09 23:12 [gentoo-dev] Modular X update Donnie Berkholz
2005-12-10  0:52 ` Martin Schlemmer
2005-12-10  1:05   ` Donnie Berkholz
2005-12-10 22:32 ` Ben Skeggs [this message]
2005-12-11  1:00   ` Donnie Berkholz
2005-12-11  1:12     ` Ben Skeggs

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=1134253921.29488.10.camel@araqiel.keine.ath.cx \
    --to=darktama@iinet.net.au \
    --cc=gentoo-dev@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