I've changed my mach64's cvsbld and dripkg scripts to have separate
build trees (so there are no *.o anymore in the DRM dir), just install
the DDX drivers that belong to driver (so there is no r128, radeon along
with the ati driver), and just install the device dependent drivers (no
lib{GL,drm,Core}.a).

This should result in a (hopefully) more clean install, besides of a 1
Mb reduction in the download file.

***NOTE***: If you have installed a previous snapshot please uninstall
_before_ installing this one due to eventual incompatibilities in libGL.
You can do that by using the install script from the previous snapshot
(sh install.sh restore) or, in alternative, reinstalling the X rpm (rpm
-Uvh --force XFree-...).

I would also like to point out that at this moment the
mach64-0-0-3-branch, from where this snapshot was taken, is perfectly
usable with almost the same level of functionality given by the previous
mach64-0-0-2-branch except some remaining glitches.

It's now the right time for testing, especially for regression bugs.
Please restrain from using excessive resolutions or any memory consuming
options in your OpenGL applications when testing to avoid problems with
lack of free onboard memory due to absence of AGP texturing - there is
nothing we can do about that right now and it would hide the existing
bugs that we can and want to fix.

The snapshot is available at
http://mefriss1.swan.ac.uk/~jfonseca/dri/packages/bleeding-edge/mach64-20020313-1542-i386.tar.bz2

At this time there still is no changelog available. Binary packages will
continue to be made unconditionally on a 4hr interval. To track the
changes consider subscribing to the dri-patches mailing list (low
traffic about 20 msgs per week) since not all changes are posted here.
I'll eventually try to find a way to generate a changelog automatically
but it won't happen soon, sorry.

Regards,

Jose Fonseca


_______________________________________________
Dri-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/dri-devel

Reply via email to