Re: [Dri-devel] DRI binary snapshots enquires

[Jens O. <je...@tu...>]

Alan Hourihane wrote:
> 
> On Wed, Feb 20, 2002 at 04:19:04AM +0000, Keith Whitwell wrote:
> > > Daryll mentioned them and said he would try to contact Alan. I don't have
> > > those scripts.
> >
> > I saw them recently somewhere - maybe on the dri website.  I'm not sure
> > where.  Alan?
> >
> Yes, the scripts got committed into the CVS.
> 
> Just 'checkout scripts' and you'll get them.
> 
> The first, is 'dripkg.sh' which takes a fully checked out and built
> DRI tree and packages up the driver. Look at the top of the file for
> usage instructions. Currently only tgz files are supported. This script
> has to be executed with the second script in the present working
> directory, as it gets copied into the tgz.
> 
> Then, the user extracts the tgz file, and executes the 'install.sh'
> and bingo, all done.
> 
> Now that they're in CVS, we can track them a lot easier too.

Alan,

I've been playing with your scripts and I'm impressed with the level of
functionality you have.  I do have a few questions probably based on my
inexperience with your scripts.

First, what are the base requirements before installation?  It looks
like XFree86 4.x and Linux Kernel 2.4.x are required and checked for by
the install script.  Are the DRI sources required as well?  It looks
like my DRM kernel modules sources are symbolic links to source files
that don't get included in the tar ball.

Second, how much do we want to upgrade (replace)?  It looks like the
scripts upgrade the OpenGL API libraries (libGL & libGLU); internal core
libraries (libglx, libGLcore, libdri & libdrm), DRM kernel modules (all
of them?) and user level drivers (2D and 3d).  I can see how replacing
all of these would increase our chance of success--however, what does
this do to compatability with older (or other) drivers.

Thanks,
Jens

--                             /\
         Jens Owen            /  \/\ _    
  je...@tu...  /    \ \ \   Steamboat Springs, Colorado