Xorg 7.2 RC2

Todd Kover kovert at omniscient.com
Sun Nov 19 10:33:29 PST 2006

 > Now available:
 > http://xorg.freedesktop.org/releases/development/X11R7.2-RC2/
 > Now with functional everything directory, that really does include
 > everything!  Man that's painful.  I think I have the algorithm for
 > release inheritance worked out now though.

By "everything" do you mean that 7.1 and 7.0 don't need to be consulted
for versions of some things?  If so...

As has been noted by others, libX11- requires 7.0.6 but 7.2-RC2
contains 7.0.5.

I also found that it requires libxtrans 1.0.0 was in 7.0, 1.0.2 is the
latest released).

It also appears to require libxcb, which hasn't been released and isn't
contained in the everything directory, though 1.0rc3 is out (aka 0.9.93)
and >=0.9.92 is required.

Also, what's the best way to build everything?  I know about
build-from-tarballs.sh in util/modular in git, but there's a *lot* of
things in there that aren't in the 7.2 directory (which leads me to the
question about 'everything' above).  For example:

	libAppleWM depends on libXext (I went with 1.0.2)
	libfontenc (1.0.2 is in 7.1, but 1.0.3 is out, I went with 1.0.2)
	libICE (1.0.1 is in 7.1, but 1.0.2 is out, I went with 1.0.1)
	libSM (1.0.0 is in 7.1, but 1.0.2 is out, I went with 1.0.0)
	libXpm ( is in 7.1, but 3.5.6 is out, I went with
	libXcomposite ( is in 7.1, but 0.3.1 is out, I went with
	libXrender (0.9.1 in 7.1, 0.9.2 out, used 0.9.1)
	libXcursor (1.1.6 in 7.1, 1.1.8 out, used 1.1.6)    
	libXevie (1.0.1 in 7.1, 1.0.2 out, used 1.0.1)
	libXfont (1.1.0 in 7.1, 1.2.3 out, used 1.1.0)
	libXfontcache (1.0.2 in 7.1, 1.0.3 out, used 1.0.2)

jhbuild seems like it is really meant for git or after you've downloaded
all the tarballs, though I didn't spend an extensive amount of time
looking into it (looked like much more flexibility than was necesary for
a simple build).

Before I start making an exhaustive list of mismatches, I wanted to make
sure that this was expected behavior.

I did not compare the modular directories to see if everything was there
but spot checking indicated no.

It would be *really really* handy if there was a modularlist file or
some such in 'everything' that simply listed all the tarballs that
were required and it was maintained from release to release so as to
avoid having to patch together earlier katamaris (as I understand the
terminology).  If I can get some direction on the dependancy issues and
what's up with the use of earlier versions, I'll gladly compile this for

I also noticed that ftp was disfunctional (unresolvable symlinks in the
chroot'd environment, I think), which left a really nasty invocation of
wget to download all the bz2 files.  I can't help but wonder if there's
a better way I'm just not aware of.

FWIW, I'm building on NetBSD 3.0/i386 and am building on a box without
any X (or, more to the point, in an environment with no X components on
the path).  I've found some OS specific issues, but I guess those are to
be reported independantly to the maintainers and not what you're looking
for in RC testing?


More information about the xorg mailing list