On Sat, Jul 12, 2008 at 8:09 PM, Charles Smith <[EMAIL PROTECTED]> wrote: > Good afternoon! > > In xenocara/MODULES file a "needs-update" entry, eg by neomagic, > can provoke errors, like PR pending/5836 [0]? > The PR in short: > On i386 ThinkPad 600X (NeoMagic 256ZX NM2360) doesn't work > WindowMaker since 2008.04.10 (or before too, that was my first test > after 4.3 RELEASE branch fork.) > With 4.3 RELEASE works. > The very odd thing: cwm, fvwm; and icewm from ports work. > All application works, that I use. > WindowMaker didn't change since 2007.09.15. > > > After branch fork in xenocara/MODULES file the neomagic has been > updated two times: > on 2008.03.19 from 1.1.1 to 1.2.0 and on 2008.05.21 to 1.2.1. > In xenocara/driver/xf86-video-neomagic/ directory remained 1.1.1. > The "needs-update" appeared with 1.2.0. > Are they not in sync? > Is this rate major update? > > Are the "needs-update" entries like as "public todo lists"?
the MODULES file tracks the revisions of the modules that are released by X.Org developpers. I mark a module as 'needs-update' whenever the most recently released version is newer than the one in Xenocara. So yes, it's more or less like a todo list. Not all updates are equal though. Many of the modules that stay in 'needs-update' for a long time do so because the upstream update doesn't bring anything to the xserver 1.4.x that we use in Xenocara. For instance, the changes in the neomagic driver that you saw are done to cope with features of the xserve 1.5 branch which is not used yet. I doubt they will help in your case. (I will try to have a look at it separatly in the next days). Other modules stay in this state just because we know the newer versions have some regressions that make them less useful than the current version in Xenocara. But this information is not explicited here. And finally many modules also stay un-updated just because of lack of interest/slacking on our side. -- Matthieu Herrb
