[oe] RFC: diet-x11, small-x11 and fat-x11
koen at dominion.kabel.utwente.nl
Tue Feb 6 15:32:22 CET 2007
-----BEGIN PGP SIGNED MESSAGE-----
Richard Purdie schreef:
> On Tue, 2007-02-06 at 13:31 +0100, Koen Kooi wrote:
>> Richard Purdie schreef:
>>> If we are going down this route, we should probably have applications
>>> say which flavour of libx11 they want through some virtual namespaces.
>>> virtual/libx11 would mean they'll work with any of the versions.
>> It basically boils down to:
>> a) I need basic x11 (gtk+, qt, etc)
>> b) I need cms (rxvt, icewm) (+32kB iirc)
>> c) I need xkb (xserver-xorg, xkb*) (+80kB iirc)
>> d) I need obsolete stuff (Xaw) (+2MB iirc)
> Are those compressed or uncompressed sizes?
Compressed, armv5te :( We should check those again including multiple architectures.
> For the sake of 100kb
> uncompressed, I'm tempted to suggest adding features to the basic x11...
>> a -> libx11-minimal.bb
>> b -> libx11-cms.bb
>> c -> libx11-cms-xkb.bb
>> d -> libx11-full.bb
>> Is that like you want?
> Kind of.
> libx11-minimal: RPROVIDES = "virtual/libx11"
> libx11-xkb: RPROVIDES = "virtual/libx11 virtual/libx11-xkb"
> libx11-full: RPROVIDES = "virtual/libx11 virtual/libx11-xkb virtual/libx11-full"
> (along with whatever the magic is to say they're equivalent and replace
> each other)
> Then anything requiring Xaw can RDEPENDS = "virtual/libx11-full" etc.
After all that we still need a way to clean staging from time to time to avoid linking
everything to the full one. (packaged-staging?)
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
-----END PGP SIGNATURE-----
More information about the Openembedded-devel