Re: New Binary modules from CVS
Torgeir Veimo <[email protected]>
| Newsgroups | gmane.comp.xfree86.forum |
|---|---|
| Message-ID | <[email protected]> |
On Wed, 2003-04-16 at 20:04, Alan Hourihane wrote: > For those who are not subscribed to devel@ or xfree86@ I thought this > might be interesting for others. Would it be possible to get a single concatenated changelog file of cvs commits available without downloading and unpacking the distribution? > Alan. > > ----- Forwarded message from Alan Hourihane <[email protected]> ----- > > To: [email protected] > Cc: [email protected] > Subject: New Binary modules from CVS > > From tonight, I'm starting a build of the latest full release version of XFree86 > (being 4.3.0), but including the latest drivers from CVS and publishing > these drivers on my home page at http://www.xfree86.org/~alanh. I hope > to automate the process fully and so we can get nightly builds done, but > over the next few days they'll be updated sporadically. > > This is an experimental test to see how well I can manage this, but it > allows those who need a bugfix from the CVS or a completely new driver > that's been committed to CVS to use it with the current full release > version of XFree86 and hopefully suffer no versioning problems. But that > remains to be seen, hence this test. > > The first snapshot of the binary modules are up for x86 architectures > only at the moment. I intend to add alpha, ppc and possibly sparc at > some future date. > > This is a big leap forward for those who can't or don't want to build > the whole X tree and just need driver support or bug fix for their > video card. > > This process may also be extended for other modules with XFree86 if > this initial test goes well. > > Any comments of feedback on this is most welcome. > > Note: if you do attempt this, make sure you back up your old driver > module first. > > Alan. > _______________________________________________ > Forum mailing list > [email protected] > http://XFree86.Org/mailman/listinfo/forum -- Torgeir Veimo <[email protected]>