[ANNOUNCE] A Build System For X.Org Modular

[Egbert Eich]

Luca Dionisi writes:
 > 
 > What I meant was a little different.
 > For what I understand, when a new set of tarballs for X.org get
 > released, someone for a specific distro has to build them, prepare
 > a set of packages (RPM or similar), set the needed dependency
 > bits (specific to that distro) and so on. Only after that phase, the
 > specific packaging system for end users could be used.
 > Am I wrong?
 > Perhaps, testing a single new piece of code is trivial only if that new
 > code doesn't use a new lib, which uses a new extension,
 > which in turn uses a new version of the server and so on.
 > But I admit that I'm talking about something I don't master.
 > 

Right. The tool was to ease testing of different bits without having
to move away possibly changed dependencies out of the way.
Libraries should provide abi compatibility. However when building
against installed pieces you can still run into issues.
If your pkgconfig test tells you you need a new version of something
you'd have to manually get this first, build and install it. 
For a quick test this time consuming. The build system allows you
to fire up the build and run it unattended.

Cheers,
	Egbert.