On Wed, 2002-10-02 at 12:19, Dieter Nützel wrote:
> > Perhaps we need to produce binary snapshots for each driver that
> > includes only the device-specific stuff (kinda like what dripkg.sh does
> > now) and then have a separate snapshot for the libraries (particularly
> > the GL libraries) which you unpack over the driver snapshot, i.e. if you
> > have an r200 on linux-i386, you'd get r200-20021003-linux-i386.tar.bz2
> > and libs-20021003-linux-i386.tar.bz2; untar the r200 tarball, then the
> > libs tarball; and then proceed to install as usual. (I don't see
> > anything in http://dri.sourceforge.net/snapshots/ that looks like it
> > might be extra libraries.)
>
> I think NOT.
Try it, you might like it.
> The snapshots are an additional service to have a wider basis for testing.
> Endusers should stay with there distros (they are for packaging all the stuff
> for the different architectures) and if they are not experienced to compile
> the current XFree/DRI CVS trees themself they should stay away.
Which is it, then: Snapshots or no snapshots? The current snapshots (for
linux-i386) don't work unless you have Red Hat 8.0 and/or glibc-2.3; I'm
not even sure that they work on that platform. Broken snapshots are
worse than no snapshots at all (you can't download something that isn't
going to work if it isn't there).
--
Andy Dustman PGP: 0x930B8AB6
@ .net http://dustman.net/andy
"Cogito, ergo sum." -- Rene Descartes
"I yam what I yam and that's all what I yam." -- Popeye
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel
