During the early Xorg-7 modular days, we hit a nasty bug where applications were crashing after updating a few of the modular packages.
http://wiki.linuxfromscratch.org/blfs/ticket/1877 It was determined that we should just stick with the package versions announced with the Xorg release and only backport security fixes. Having been following the Xorg development a lot more closely for a while and built the modular packages many times, I'd like to change this policy. What caused that bug was updating packages that had undergone major changes scheduled for the next Xorg release. In that case it was compositeproto-0.3, fixesproto-4.0 and libXcomposite-0.3. We'd hit the same issue right now if we tried to update to inputproto-1.4 and libXi-1.1.0. I'm proposing that we should update packages that have patchlevel releases (third number) in the same cycle. We're missing out on some key bug fixes and forced to carry around patches for a bunch of packages with the current policy. http://linuxfromscratch.org/pipermail/blfs-support/2006-December/061719.html http://lists.freedesktop.org/archives/xorg/2007-January/021193.html Thinking about libXi again, while 1.1.0 would break things for us (all Daniel Stone's input hotplugging stuff is there), 1.0.2 contains a bug fix we'd probably like. http://gitweb.freedesktop.org/?p=xorg/lib/libXi.git;a=commitdiff;h=f0f5fb7b4eb685094fc64aa1b46573991e84589f I can produce a list of updated packages later if anyone thinks this is a good idea. I've just installed X with this policy and everything's working fine here. -- Dan -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
