[SM-Discuss] Xorg and updates -- why aren't we waiting
Andraž 'ruskie' Levstik
ruskie at codemages.net
Sat Mar 28 13:02:03 EDT 2009
:2009-03-28T10:44:Bearcat M. Şandor:
> My understanding is that xorg-server is being tested in it's own grimoire. Yet
> every other week i see someone updating libxcb or libx11 or some other X
> library and sure enough it breaks stuff. Then the commit is reverted and
> someone else does it.
Nothing is being updated. It's been reverted to fix issues. This is
stuff that got updated and then found to be broken.
> Why don't we just not update *anything* xorg-server related until that xorg
> testing grimoire is merged in to the main trunk?
> What the status on that, by the way?
It'll be merged once upstream makes the next major release X7.5. And this
is how it will be from now on. You can check the mailing list archive to
see the discussion on this earlier.
If there is any need to push something through sooner then it will be
arranged(i.e. security issues, possibly driver updates). I would
consider the following section more or less safe in most cases:
xorg-app - unless the app requires an updated lib it should be safe
xorg-util - most stuff here is hardly used. For the stuff that there is it tends to be non-breakable
xorg-font - this is generally not really an issue to update
xorg-driver - anything that isn't development version(i.e. x.999 or y.900 etc..)
xorg-doc - shouldn't be much of an issue
Another thing that might be a good idea along here is to handle mesalib
in a similar way. Or atleast anyone that updates it to go to their
homepage and look if it's a stable or devel release.
Andraž ruskie Levstik
Source Mage GNU/Linux Games/Xorg grimoire guru
More information about the SM-Discuss