[gentoo-dev] Modular X update

[gentoo-dev] Modular X update

[Donnie Berkholz]

AREAS WE NEED HELP WITH:
1) Porting applications to modular X
2) Fixing descriptions for the vast majority of modular packages.


OK, it seems like we've now got issues resolved related to the new 
virtual/x11 package. Despite all the eyes that looked at it and all the 
publicity on lists and elsewhere, we still missed the lack of stable 
keywords in it, which caused some issues when the default virtual was 
pulled from the base profile. Thanks to axxo and flameeyes for dealing 
with this while I was at lunch.

Here's roughly how it all works:

1) Users with xorg-6.x installed will continue along happily, because 
6.x PROVIDES virtual/x11 on their systems.

2) Users with no X installed will pull in the virtual/x11 package 
because there is no longer a default virtual.

3) Users with xorg-7.x installed will need all their packages updated 
for modular dependencies. There is a porting guide at 
http://dev.gentoo.org/~spyderous/xorg-x11/porting_to_modular_x_howto.txt 
  -- go ahead and run through it for your favorite packages, and file 
bugs to their maintainers with the updated dependencies.

One note for porting to modular: binary packages will require a script 
using ldd instead of one checking the compilation log. Petteri Räty has 
kindly made one available at 
http://dev.gentoo.org/~betelgeuse/scripts/checkdeps -- it depends on 
portage-utils.

While packages are being ported to modular X, you will be unable to 
upgrade any unported packages (so likely your 'world') without an entry 
in /etc/portage/profile/virtuals that emulates virtual/x11 using an 
installed package, e.g.:

virtual/x11	x11-base/xorg-x11

assuming you have the xorg-x11-7 metabuild installed.

I hope that covers pretty much everything right now.

Thanks for your patience,
Donnie
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Modular X update

[Martin Schlemmer]

[-- Attachment #1: Type: text/plain, Size: 2110 bytes --]

On Fri, 2005-12-09 at 23:12 +0000, Donnie Berkholz wrote:
> AREAS WE NEED HELP WITH:
> 1) Porting applications to modular X
> 2) Fixing descriptions for the vast majority of modular packages.
> 
> 
> OK, it seems like we've now got issues resolved related to the new 
> virtual/x11 package. Despite all the eyes that looked at it and all the 
> publicity on lists and elsewhere, we still missed the lack of stable 
> keywords in it, which caused some issues when the default virtual was 
> pulled from the base profile. Thanks to axxo and flameeyes for dealing 
> with this while I was at lunch.
> 
> Here's roughly how it all works:
> 
> 1) Users with xorg-6.x installed will continue along happily, because 
> 6.x PROVIDES virtual/x11 on their systems.
> 
> 2) Users with no X installed will pull in the virtual/x11 package 
> because there is no longer a default virtual.
> 
> 3) Users with xorg-7.x installed will need all their packages updated 
> for modular dependencies. There is a porting guide at 
> http://dev.gentoo.org/~spyderous/xorg-x11/porting_to_modular_x_howto.txt 
>   -- go ahead and run through it for your favorite packages, and file 
> bugs to their maintainers with the updated dependencies.
> 
> One note for porting to modular: binary packages will require a script 
> using ldd instead of one checking the compilation log. Petteri Räty has 
> kindly made one available at 
> http://dev.gentoo.org/~betelgeuse/scripts/checkdeps -- it depends on 
> portage-utils.
> 
> While packages are being ported to modular X, you will be unable to 
> upgrade any unported packages (so likely your 'world') without an entry 
> in /etc/portage/profile/virtuals that emulates virtual/x11 using an 
> installed package, e.g.:
> 
> virtual/x11	x11-base/xorg-x11
> 
> assuming you have the xorg-x11-7 metabuild installed.
> 
> I hope that covers pretty much everything right now.
> 

Will need to do something about the default glu/opengl/xft virtuals as
well ... (you probably did not forget this, just double checking ...)


-- 
Martin Schlemmer


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]

Re: [gentoo-dev] Modular X update

[Donnie Berkholz]

Martin Schlemmer wrote:
> Will need to do something about the default glu/opengl/xft virtuals as
> well ... (you probably did not forget this, just double checking ...)

Yep.

 From an email I sent in the past 24 hours:

Donnie Berkholz wrote:
 > Done.
 >
 > I will probably do similar for the other x11 virtuals (particularly
 > xft) soon, assuming this doesn't break too badly.
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Modular X update

[Ben Skeggs]

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

Re: [gentoo-dev] Modular X update

[Donnie Berkholz]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Ben Skeggs wrote:
| 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?

Already been fixed some hours ago.

|>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?

The other ones should just stay the same as they are. virtual/x11 was
different because it was one virtual covering something that split into
hundreds of separate packages. But xft, opengl, glu are just changing
<=xorg-x11-6.99 into libXft, mesa, mesa respectively so that will
require no porting work, just more true "virtual" packages to be added.

Thanks,
Donnie
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFDm3onXVaO67S1rtsRAjYFAJ9RHctg7zg8z8e/Ia+SFT7qbapP9QCg6qW+
6Jt04OupayM0ENoiM6GCL3Q=
=ZWXJ
-----END PGP SIGNATURE-----
-- 
gentoo-dev@gentoo.org mailing list

Re: [gentoo-dev] Modular X update

[Ben Skeggs]

Am Samstag, den 10.12.2005, 17:00 -0800 schrieb Donnie Berkholz:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Ben Skeggs wrote:
> | 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?
> 
> Already been fixed some hours ago.
Yup, I noticed that soon after I posted this.  Thanks.

> 
> |>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?
> 
> The other ones should just stay the same as they are. virtual/x11 was
> different because it was one virtual covering something that split into
> hundreds of separate packages. But xft, opengl, glu are just changing
> <=xorg-x11-6.99 into libXft, mesa, mesa respectively so that will
> require no porting work, just more true "virtual" packages to be added.
Ah, I see.  That makes sense now actually, I'll hold off modifying
packages that depend on those virtuals until the "real" virtuals for
them are in place.

Thanks,
Ben.
-- 
gentoo-dev@gentoo.org mailing list