Linked by Thom Holwerda on Tue 23rd May 2006 21:46 UTC, submitted by Joel Dahl
X11, Window Managers "Five months after release of X11R7.0, the modularized and autotooled release of the MIT Licensed X Window System source code, the X.Org Foundation has issued its first modular roll-up release. X11R7.1 supports Linux, Solaris, and BSD systems. It includes important new server and driver features for embedded systems, 64 bit platforms, enhanced operating system support, and accelerated indirect GLX support. It most importantly demonstrates to developers and industry immediate benefits of modularization."
Permalink for comment 127487
To read all comments associated with this story, please click here.
RE[3]: answered my own question
by Ookaze on Wed 24th May 2006 13:57 UTC in reply to "RE[2]: answered my own question"
Member since:

but unless you're doing this for a distribution that's being exported to multiple clients (in my case the college I work at) you won't be able to understand that this does _not_ make our lives easier

Your life being easier depends on your package manager, not on the number of packages to push.
So no, I don't understand. Or rather, yes, I know there's a big packages creation time beforehand for the maintainer. I can't deny it, I've been through it.

unfortunately I've found it much to common for instance for upstream providers to not get it in their head that people aren't always going to be installing their stuff locally, as a single user on their own machine would

So modularized X is good for you, as it solves this. So it's better now.

Some devs don't even write in DESTDIR support into their Makefiles, or, decide they'll be really cool and write up their own unique build and install system say in python or something, which will be useless to someone like me...

XOrg was full of these kind of things. Fortunately, the modularisation allowed people to spot all of these.
So it's better now.

but telling us to track 280 releases instead of one, is not doing us a favour

You sound like it was doing them a favour. It took them months to do that and autotooling everything.
It was necessary IMHO, and I don't think they did it because they are masochists.
You meant tracking 280 packages I guess. There's far less than 280 releases for this 7.1 release for example.
And if I can track releases with one script and alone, I think any distro packager can do it too, with QA.
Some packages don't even need big QA, like fonts, or old rarely used X apps.
But don't worry, I don't think the monolithic release is abandonned, IIRC a 6.9.1 is on the way.

oh about getting rid of /usr/X11, you might want to reconsider (or do what we did and make a symlink to /usr/local which is where our built stuff goes for the most part)

I initially did that and a bunch of other symlinks for 7.0. Everything has been solved before 7.1 release though (which I still haven't installed, but I don't need more than 5 packages to update I think).

some packages are pretty stupid about this (vmware comes to mind) and won't be happy unless it's there

Then these packages have to be fixed. IIRC I patched xfce-session for this for example.
My desktops are now fully functional without any symlink anymore.

anyhow, being able to specify your prefix for X isn't exactly something new. take a look at the old host.def file, there's a lot of things that you can tweak in there. (#define ProjectRoot is what your looking for)

Of course, but doing it and then have it work is something new.
Given all the hard paths removed in the XOrg code thanks to the modularisation, I doubt it would have worked (without the /usr/X11 symlink at least). Even the use of other fonts path (i.e. /usr/share/fonts) was implemented through symlinks in the monolithic package. I say no thanks : you removed them, and suddenly lots of packages that did not actually use the new paths stopped working.
For example, sth as essential as xterm, which is outside XOrg releases, had to be fixed.
Really, IMHO, the modularisation had a LOT of benefits already.

Reply Parent Score: 1