Re: Update on status of CVS DRI packages.
On Mon, Mar 26, 2001 at 02:52:57PM -0500, Zephaniah E. Hull wrote: > > Are you sure both are needed? Your xserver-xfree86-dri package should > > provide a superset of the modules that my xserver-xfree86 package does. > > Actually it is a subset, providing only what is used by the DRI code and > leaving the rest to your packages, otherwise I would simply conflict > with xserver-xfree86. > > The reason is two fold, the first is that it is roughly what the DRI > project is providing in other forms. > > The second is that the DRI cvs tree does not include everything that the > X cvs tree does, trying to provide a superset would be quite a bit more > work all around. Okay. How about this? 1) Don't ship config or templates, and remove all debconf stuff from the xserver-xfree86(-dri) maintainer scripts. 2) Go ahead and do a dpkg-divert in your postinst of XFree86 to XFree86-dri. 3) Use message() in the xserver package postinst to tell the user to add the "modules-dri" path to his XF86Config-4. -- G. Branden Robinson | Debian GNU/Linux|Exercise your freedom of religion. Set [EMAIL PROTECTED] |fire to a church of your choice. http://www.debian.org/~branden/ | pgpx0s3ZRGekG.pgp Description: PGP signature
Re: Update on status of CVS DRI packages.
On Mon, Mar 26, 2001 at 02:08:53PM -0500, Branden Robinson wrote: > On Mon, Mar 26, 2001 at 01:58:00PM -0500, Zephaniah E. Hull wrote: > > After much prodding and poking I have it down to three issues, the > > naming scheme is as follows, with the issues below. > > > > xlibmesa3-dri contains libGL, libGLU, and libGLw, it also contains > > usr/X11R6/lib/modules.dri/dri/(gamma|i810|mga|r128|radeon|sis|tdfx)_driso. > > I don't think GLw is supposed to be available as a shared object. Whoops, my mistake, it is as a .a in -dev and not at all in xlibmesa3-dri. > > > xlibmesa-dri-dev contains the devel files for xlibmesa3-dri. > > > > xlibosmesa3-dri contains libOSMesa. > > > > xlibosmesa-dri-dev contains the devel files for xlibosmesa3-dri. > > Do you have any feedback for Marcelo Magallon, who, IIRC claims you don't > need to provide versions of these? I'll probably stop building them before I put things up. > > > xserver-dri contains usr/X11R6/bin/XFree86.dri and more contents for > > /usr/X11R6/lib/modules.dri. > > > > This scheme removes all need for diversions, leaving with exactly three > > issues before I can produce .debs for people to test. > > Okay, great. > > > 1: I'd really like Branden to agree to the naming scheme. > > One tweak. I think the package names should be exactly as my X package > names, with "-dri" appended. Even for the -dev packages. > > So, e.g., xlibmesa-dev-dri. Sounds reasonable. > > Also, for the sake of sheer symmetry I don't see why you can't use the > pathnames XFree86-dri and modules-dri. Done. > > > 2: Until Branden packages 4.0.3 or later I need to provide the > > XFree86.dri, and need to figure out the proper way to set > > /etc/X11/Xserver XFree86.dri. > > (Branden, can you point this out please? It should be simple.) > > Actually, it probably isn't. You need to do something akin to a > global-search and replace in debconf template names in the templates, > config, and other maintainer scripts, replacing "xserver-xfree86" with > "xserver-xfree86-dri". > > Also, you need to be sure that all references to "/usr/.../XFree86" in > these files change to "XFree86-dri". Ugh, I was hoping to avoid most of that as the dri xserver package depends on yours. (See below.) > > > 3: The XF86Config-4 needs to have two lines[1] added so X will search > > the modules.dri directory then the modules directory, I'll probably > > leave this up to the user for now. > > Yes, let's do that. Otherwise I have to hack dexconf. You can use my > message() shell function in the postinst to tell the user to do this. > > > As soon as those three have been addressed I'll put .debs up somewhere > > aptable for people to test. > > > > Zephaniah E. Hull. > > > > 1: > > ModulePath "/usr/X11R6/lib/modules.dri" > > ModulePath "/usr/X11R6/lib/modules" > > Are you sure both are needed? Your xserver-xfree86-dri package should > provide a superset of the modules that my xserver-xfree86 package does. Actually it is a subset, providing only what is used by the DRI code and leaving the rest to your packages, otherwise I would simply conflict with xserver-xfree86. The reason is two fold, the first is that it is roughly what the DRI project is providing in other forms. The second is that the DRI cvs tree does not include everything that the X cvs tree does, trying to provide a superset would be quite a bit more work all around. Zephaniah E. Hull. > > -- > G. Branden Robinson |"To be is to do" -- Plato > Debian GNU/Linux|"To do is to be" -- Aristotle > [EMAIL PROTECTED] |"Do be do be do" -- Sinatra > http://www.debian.org/~branden/ | -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. I am an "expert". Fear me, for I will wreak untold damage upon anything I can get my grubby hands on. -- Matt McLeod on ASR. pgpmyvhkyO4sz.pgp Description: PGP signature
Re: Update on status of CVS DRI packages.
On Mon, Mar 26, 2001 at 01:58:00PM -0500, Zephaniah E. Hull wrote: > After much prodding and poking I have it down to three issues, the > naming scheme is as follows, with the issues below. > > xlibmesa3-dri contains libGL, libGLU, and libGLw, it also contains > usr/X11R6/lib/modules.dri/dri/(gamma|i810|mga|r128|radeon|sis|tdfx)_dri.so. I don't think GLw is supposed to be available as a shared object. > xlibmesa-dri-dev contains the devel files for xlibmesa3-dri. > > xlibosmesa3-dri contains libOSMesa. > > xlibosmesa-dri-dev contains the devel files for xlibosmesa3-dri. Do you have any feedback for Marcelo Magallon, who, IIRC claims you don't need to provide versions of these? > xserver-dri contains usr/X11R6/bin/XFree86.dri and more contents for > /usr/X11R6/lib/modules.dri. > > This scheme removes all need for diversions, leaving with exactly three > issues before I can produce .debs for people to test. Okay, great. > 1: I'd really like Branden to agree to the naming scheme. One tweak. I think the package names should be exactly as my X package names, with "-dri" appended. Even for the -dev packages. So, e.g., xlibmesa-dev-dri. Also, for the sake of sheer symmetry I don't see why you can't use the pathnames XFree86-dri and modules-dri. > 2: Until Branden packages 4.0.3 or later I need to provide the > XFree86.dri, and need to figure out the proper way to set > /etc/X11/Xserver XFree86.dri. > (Branden, can you point this out please? It should be simple.) Actually, it probably isn't. You need to do something akin to a global-search and replace in debconf template names in the templates, config, and other maintainer scripts, replacing "xserver-xfree86" with "xserver-xfree86-dri". Also, you need to be sure that all references to "/usr/.../XFree86" in these files change to "XFree86-dri". > 3: The XF86Config-4 needs to have two lines[1] added so X will search > the modules.dri directory then the modules directory, I'll probably > leave this up to the user for now. Yes, let's do that. Otherwise I have to hack dexconf. You can use my message() shell function in the postinst to tell the user to do this. > As soon as those three have been addressed I'll put .debs up somewhere > aptable for people to test. > > Zephaniah E. Hull. > > 1: > ModulePath "/usr/X11R6/lib/modules.dri" > ModulePath "/usr/X11R6/lib/modules" Are you sure both are needed? Your xserver-xfree86-dri package should provide a superset of the modules that my xserver-xfree86 package does. -- G. Branden Robinson |"To be is to do" -- Plato Debian GNU/Linux|"To do is to be" -- Aristotle [EMAIL PROTECTED] |"Do be do be do" -- Sinatra http://www.debian.org/~branden/ | pgpL8hdMOyUZ3.pgp Description: PGP signature
Re: Update on status of CVS DRI packages.
On Mon, Mar 26, 2001 at 02:52:57PM -0500, Zephaniah E. Hull wrote: > > Are you sure both are needed? Your xserver-xfree86-dri package should > > provide a superset of the modules that my xserver-xfree86 package does. > > Actually it is a subset, providing only what is used by the DRI code and > leaving the rest to your packages, otherwise I would simply conflict > with xserver-xfree86. > > The reason is two fold, the first is that it is roughly what the DRI > project is providing in other forms. > > The second is that the DRI cvs tree does not include everything that the > X cvs tree does, trying to provide a superset would be quite a bit more > work all around. Okay. How about this? 1) Don't ship config or templates, and remove all debconf stuff from the xserver-xfree86(-dri) maintainer scripts. 2) Go ahead and do a dpkg-divert in your postinst of XFree86 to XFree86-dri. 3) Use message() in the xserver package postinst to tell the user to add the "modules-dri" path to his XF86Config-4. -- G. Branden Robinson | Debian GNU/Linux|Exercise your freedom of religion. Set [EMAIL PROTECTED] |fire to a church of your choice. http://www.debian.org/~branden/ | PGP signature
Update on status of CVS DRI packages.
After much prodding and poking I have it down to three issues, the naming scheme is as follows, with the issues below. xlibmesa3-dri contains libGL, libGLU, and libGLw, it also contains usr/X11R6/lib/modules.dri/dri/(gamma|i810|mga|r128|radeon|sis|tdfx)_dri.so. xlibmesa-dri-dev contains the devel files for xlibmesa3-dri. xlibosmesa3-dri contains libOSMesa. xlibosmesa-dri-dev contains the devel files for xlibosmesa3-dri. xserver-dri contains usr/X11R6/bin/XFree86.dri and more contents for /usr/X11R6/lib/modules.dri. This scheme removes all need for diversions, leaving with exactly three issues before I can produce .debs for people to test. 1: I'd really like Branden to agree to the naming scheme. 2: Until Branden packages 4.0.3 or later I need to provide the XFree86.dri, and need to figure out the proper way to set /etc/X11/Xserver XFree86.dri. (Branden, can you point this out please? It should be simple.) 3: The XF86Config-4 needs to have two lines[1] added so X will search the modules.dri directory then the modules directory, I'll probably leave this up to the user for now. As soon as those three have been addressed I'll put .debs up somewhere aptable for people to test. Zephaniah E. Hull. 1: ModulePath "/usr/X11R6/lib/modules.dri" ModulePath "/usr/X11R6/lib/modules" -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Seen on the back of a T-Shirt: "I am a bomb technician. If you see me running, try to keep up." pgpNDwiPbQHvc.pgp Description: PGP signature
Re: Update on status of CVS DRI packages.
On Mon, Mar 26, 2001 at 02:08:53PM -0500, Branden Robinson wrote: > On Mon, Mar 26, 2001 at 01:58:00PM -0500, Zephaniah E. Hull wrote: > > After much prodding and poking I have it down to three issues, the > > naming scheme is as follows, with the issues below. > > > > xlibmesa3-dri contains libGL, libGLU, and libGLw, it also contains > > usr/X11R6/lib/modules.dri/dri/(gamma|i810|mga|r128|radeon|sis|tdfx)_driso. > > I don't think GLw is supposed to be available as a shared object. Whoops, my mistake, it is as a .a in -dev and not at all in xlibmesa3-dri. > > > xlibmesa-dri-dev contains the devel files for xlibmesa3-dri. > > > > xlibosmesa3-dri contains libOSMesa. > > > > xlibosmesa-dri-dev contains the devel files for xlibosmesa3-dri. > > Do you have any feedback for Marcelo Magallon, who, IIRC claims you don't > need to provide versions of these? I'll probably stop building them before I put things up. > > > xserver-dri contains usr/X11R6/bin/XFree86.dri and more contents for > > /usr/X11R6/lib/modules.dri. > > > > This scheme removes all need for diversions, leaving with exactly three > > issues before I can produce .debs for people to test. > > Okay, great. > > > 1: I'd really like Branden to agree to the naming scheme. > > One tweak. I think the package names should be exactly as my X package > names, with "-dri" appended. Even for the -dev packages. > > So, e.g., xlibmesa-dev-dri. Sounds reasonable. > > Also, for the sake of sheer symmetry I don't see why you can't use the > pathnames XFree86-dri and modules-dri. Done. > > > 2: Until Branden packages 4.0.3 or later I need to provide the > > XFree86.dri, and need to figure out the proper way to set > > /etc/X11/Xserver XFree86.dri. > > (Branden, can you point this out please? It should be simple.) > > Actually, it probably isn't. You need to do something akin to a > global-search and replace in debconf template names in the templates, > config, and other maintainer scripts, replacing "xserver-xfree86" with > "xserver-xfree86-dri". > > Also, you need to be sure that all references to "/usr/.../XFree86" in > these files change to "XFree86-dri". Ugh, I was hoping to avoid most of that as the dri xserver package depends on yours. (See below.) > > > 3: The XF86Config-4 needs to have two lines[1] added so X will search > > the modules.dri directory then the modules directory, I'll probably > > leave this up to the user for now. > > Yes, let's do that. Otherwise I have to hack dexconf. You can use my > message() shell function in the postinst to tell the user to do this. > > > As soon as those three have been addressed I'll put .debs up somewhere > > aptable for people to test. > > > > Zephaniah E. Hull. > > > > 1: > > ModulePath "/usr/X11R6/lib/modules.dri" > > ModulePath "/usr/X11R6/lib/modules" > > Are you sure both are needed? Your xserver-xfree86-dri package should > provide a superset of the modules that my xserver-xfree86 package does. Actually it is a subset, providing only what is used by the DRI code and leaving the rest to your packages, otherwise I would simply conflict with xserver-xfree86. The reason is two fold, the first is that it is roughly what the DRI project is providing in other forms. The second is that the DRI cvs tree does not include everything that the X cvs tree does, trying to provide a superset would be quite a bit more work all around. Zephaniah E. Hull. > > -- > G. Branden Robinson |"To be is to do" -- Plato > Debian GNU/Linux|"To do is to be" -- Aristotle > [EMAIL PROTECTED] |"Do be do be do" -- Sinatra > http://www.debian.org/~branden/ | -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. I am an "expert". Fear me, for I will wreak untold damage upon anything I can get my grubby hands on. -- Matt McLeod on ASR. PGP signature
Re: Update on status of CVS DRI packages.
On Mon, Mar 26, 2001 at 01:58:00PM -0500, Zephaniah E. Hull wrote: > After much prodding and poking I have it down to three issues, the > naming scheme is as follows, with the issues below. > > xlibmesa3-dri contains libGL, libGLU, and libGLw, it also contains > usr/X11R6/lib/modules.dri/dri/(gamma|i810|mga|r128|radeon|sis|tdfx)_dri.so. I don't think GLw is supposed to be available as a shared object. > xlibmesa-dri-dev contains the devel files for xlibmesa3-dri. > > xlibosmesa3-dri contains libOSMesa. > > xlibosmesa-dri-dev contains the devel files for xlibosmesa3-dri. Do you have any feedback for Marcelo Magallon, who, IIRC claims you don't need to provide versions of these? > xserver-dri contains usr/X11R6/bin/XFree86.dri and more contents for > /usr/X11R6/lib/modules.dri. > > This scheme removes all need for diversions, leaving with exactly three > issues before I can produce .debs for people to test. Okay, great. > 1: I'd really like Branden to agree to the naming scheme. One tweak. I think the package names should be exactly as my X package names, with "-dri" appended. Even for the -dev packages. So, e.g., xlibmesa-dev-dri. Also, for the sake of sheer symmetry I don't see why you can't use the pathnames XFree86-dri and modules-dri. > 2: Until Branden packages 4.0.3 or later I need to provide the > XFree86.dri, and need to figure out the proper way to set > /etc/X11/Xserver XFree86.dri. > (Branden, can you point this out please? It should be simple.) Actually, it probably isn't. You need to do something akin to a global-search and replace in debconf template names in the templates, config, and other maintainer scripts, replacing "xserver-xfree86" with "xserver-xfree86-dri". Also, you need to be sure that all references to "/usr/.../XFree86" in these files change to "XFree86-dri". > 3: The XF86Config-4 needs to have two lines[1] added so X will search > the modules.dri directory then the modules directory, I'll probably > leave this up to the user for now. Yes, let's do that. Otherwise I have to hack dexconf. You can use my message() shell function in the postinst to tell the user to do this. > As soon as those three have been addressed I'll put .debs up somewhere > aptable for people to test. > > Zephaniah E. Hull. > > 1: > ModulePath "/usr/X11R6/lib/modules.dri" > ModulePath "/usr/X11R6/lib/modules" Are you sure both are needed? Your xserver-xfree86-dri package should provide a superset of the modules that my xserver-xfree86 package does. -- G. Branden Robinson |"To be is to do" -- Plato Debian GNU/Linux|"To do is to be" -- Aristotle [EMAIL PROTECTED] |"Do be do be do" -- Sinatra http://www.debian.org/~branden/ | PGP signature
Update on status of CVS DRI packages.
After much prodding and poking I have it down to three issues, the naming scheme is as follows, with the issues below. xlibmesa3-dri contains libGL, libGLU, and libGLw, it also contains usr/X11R6/lib/modules.dri/dri/(gamma|i810|mga|r128|radeon|sis|tdfx)_dri.so. xlibmesa-dri-dev contains the devel files for xlibmesa3-dri. xlibosmesa3-dri contains libOSMesa. xlibosmesa-dri-dev contains the devel files for xlibosmesa3-dri. xserver-dri contains usr/X11R6/bin/XFree86.dri and more contents for /usr/X11R6/lib/modules.dri. This scheme removes all need for diversions, leaving with exactly three issues before I can produce .debs for people to test. 1: I'd really like Branden to agree to the naming scheme. 2: Until Branden packages 4.0.3 or later I need to provide the XFree86.dri, and need to figure out the proper way to set /etc/X11/Xserver XFree86.dri. (Branden, can you point this out please? It should be simple.) 3: The XF86Config-4 needs to have two lines[1] added so X will search the modules.dri directory then the modules directory, I'll probably leave this up to the user for now. As soon as those three have been addressed I'll put .debs up somewhere aptable for people to test. Zephaniah E. Hull. 1: ModulePath "/usr/X11R6/lib/modules.dri" ModulePath "/usr/X11R6/lib/modules" -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Seen on the back of a T-Shirt: "I am a bomb technician. If you see me running, try to keep up." PGP signature
Re: CVS DRI packages.
On Sat, Mar 24, 2001 at 09:00:51PM -0500, Zephaniah E. Hull wrote: > I am currently about ready to start testing of .debs out of the DRI cvs > tree. *round of applause* Thank you very, very, much. I take it you'll post details here when you have debs for us to test. Jules
Re: CVS DRI packages.
On Sat, Mar 24, 2001 at 09:00:51PM -0500, Zephaniah E. Hull wrote: > I am currently about ready to start testing of .debs out of the DRI cvs > tree. *round of applause* Thank you very, very, much. I take it you'll post details here when you have debs for us to test. Jules -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS DRI packages.
On Sun, Mar 25, 2001 at 05:15:09AM +0200, Marcelo E. Magallon wrote: > I'm sorry, I forgot one important bit. > > >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > > > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. > > You might want to provide > xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (or whatever > the actual path is), as every now and then the DRM modules in the > kernel get out of sync with the ones in CVS. Yes, this should be provided. Shouldn't it be provided in a package like drm- modules-src, though, like lm-sensors-src and alsa-src? This would mean breaking that part of the trunk off and placing it in /usr/src/modules/drm or the like, and having the dri modules built whenever make-kpkg makes a modules_image. I'm getting ahead of Zeph here, though, and I'm of no skill to volunteer help... :) -- -=|JP|=-"This space intentionally left blank." Jon Pennington | Debian 2.4 -o) [EMAIL PROTECTED] | Auto Enthusiast/\\ Kansas City, MO, USA| Proud Husband and Father _\_V
Re: CVS DRI packages.
On Sun, Mar 25, 2001 at 05:15:09AM +0200, Marcelo E. Magallon wrote: > I'm sorry, I forgot one important bit. > > >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > > > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. > > You might want to provide > xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (or whatever > the actual path is), as every now and then the DRM modules in the > kernel get out of sync with the ones in CVS. Yes, this should be provided. Shouldn't it be provided in a package like drm- modules-src, though, like lm-sensors-src and alsa-src? This would mean breaking that part of the trunk off and placing it in /usr/src/modules/drm or the like, and having the dri modules built whenever make-kpkg makes a modules_image. I'm getting ahead of Zeph here, though, and I'm of no skill to volunteer help... :) -- -=|JP|=-"This space intentionally left blank." Jon Pennington | Debian 2.4 -o) [EMAIL PROTECTED] | Auto Enthusiast/\\ Kansas City, MO, USA| Proud Husband and Father _\_V -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS DRI packages.
On Sat, Mar 24, 2001 at 11:14:20PM -0500, Branden Robinson wrote: > On Sat, Mar 24, 2001 at 09:00:51PM -0500, Zephaniah E. Hull wrote: > > The 4 mesa packages are obvious, they will conflict, provide, and > > replace their counterparts[1]. > > > > Now, xserver-dri is a little less obvious, it depends on > > xserver-xfree86, but also needs to override 14 files[2] from it. > > I see superscripts but no footnotes. See my reply to Marcelo E. Magallon for said footnotes. Also, what he pointed out for the X server should work, not sure why I did not remember that. Zephaniah E. Hull. > > -- > G. Branden Robinson |Never underestimate the power of human > Debian GNU/Linux|stupidity. > [EMAIL PROTECTED] |-- Robert Heinlein > http://www.debian.org/~branden/ | -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Knghtbrd: Any suggestions on how to semi-easily make $55? Mercury: if you went and beat the crap out of some QL people I'm sure you'd get at least tenfold that from people expressing their gratitude ;> (my luck he takes that seriously hehe) Knghtbrd: This channel is logged.. [msg(Knghtbrd)] If you can provide transportation.. <=:] [Knghtbrd([EMAIL PROTECTED])] hahahaha pgpBggOOTJA4I.pgp Description: PGP signature
Re: CVS DRI packages.
On Sat, Mar 24, 2001 at 09:00:51PM -0500, Zephaniah E. Hull wrote: > The 4 mesa packages are obvious, they will conflict, provide, and > replace their counterparts[1]. > > Now, xserver-dri is a little less obvious, it depends on > xserver-xfree86, but also needs to override 14 files[2] from it. I see superscripts but no footnotes. -- G. Branden Robinson |Never underestimate the power of human Debian GNU/Linux|stupidity. [EMAIL PROTECTED] |-- Robert Heinlein http://www.debian.org/~branden/ | pgpJahqwQJnd1.pgp Description: PGP signature
Re: CVS DRI packages.
>> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > It might be possible to get X to search a different module path first, > but all examples of that turn out to be very ugly in the config file, > I'll keep poking. Ah, yes, that's actually cleaner. For the X server, you could change the symlink in /etc/X11/X, given there's a nice debconf interface and all that. -- Marcelo
Re: CVS DRI packages.
On Sun, Mar 25, 2001 at 05:15:09AM +0200, Marcelo E. Magallon wrote: > I'm sorry, I forgot one important bit. > > >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > > > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. > > You might want to provide > xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (or whatever > the actual path is), as every now and then the DRM modules in the > kernel get out of sync with the ones in CVS. That will be after I get the basics working, likely provided in the same manner as other sets of kernel models. Zephaniah E. Hull. > > -- > Marcelo -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. It's also your right to f*ck up your own version of Linux, but you're not getting close to mine. Linus pgpUVxig8K3Qj.pgp Description: PGP signature
Re: CVS DRI packages.
On Sun, Mar 25, 2001 at 05:10:47AM +0200, Marcelo E. Magallon wrote: > >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > > > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. > > I would drop the xlibosmesa packages. libOSMesa is a software only > client side off-screen rendering library. > > > The 4 mesa packages are obvious, they will conflict, provide, and > > replace their counterparts[1]. > > You forgot the footnotes. Ahh, yes, my mistake. 1: Just s/-dri//g to get their counterparts. 2: I'll append the list to the bottom of this message. > > > Right now I'm undecided on how to do the override, calling dpkg-divert > > from the preinst and postrm would work, but seems to be more of a kludge. > > Is there other way? I actually think it's safer that way. Using alternatives might work, but Branden would have to very explicitly support that. It might be possible to get X to search a different module path first, but all examples of that turn out to be very ugly in the config file, I'll keep poking. Hopefully Branden will have some ideas. Zephaniah E. Hull. > > -- > Marcelo usr/X11R6/bin/XFree86 usr/X11R6/lib/modules/drivers/ati_drv.o usr/X11R6/lib/modules/drivers/atimisc_drv.o usr/X11R6/lib/modules/drivers/glint_drv.o usr/X11R6/lib/modules/drivers/i810_drv.o usr/X11R6/lib/modules/drivers/mga_drv.o usr/X11R6/lib/modules/drivers/r128_drv.o usr/X11R6/lib/modules/drivers/radeon_drv.o usr/X11R6/lib/modules/drivers/tdfx_drv.o usr/X11R6/lib/modules/drivers/vga_drv.o usr/X11R6/lib/modules/extensions/libGLcore.a usr/X11R6/lib/modules/extensions/libdri.a usr/X11R6/lib/modules/extensions/libglx.a usr/X11R6/lib/modules/linux/libdrm.a -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. ``Who killed the server at the colo site?'' ``Weasel killed the server at the colo site'' ``Not me'' ``Then who?'' ``m2 killed the server at the colo site'' ... pgpwUoS2QGZjN.pgp Description: PGP signature
Re: CVS DRI packages.
I'm sorry, I forgot one important bit. >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. You might want to provide xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (or whatever the actual path is), as every now and then the DRM modules in the kernel get out of sync with the ones in CVS. -- Marcelo
Re: CVS DRI packages.
>> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. I would drop the xlibosmesa packages. libOSMesa is a software only client side off-screen rendering library. > The 4 mesa packages are obvious, they will conflict, provide, and > replace their counterparts[1]. You forgot the footnotes. > Right now I'm undecided on how to do the override, calling dpkg-divert > from the preinst and postrm would work, but seems to be more of a kludge. Is there other way? I actually think it's safer that way. -- Marcelo
Re: CVS DRI packages.
On Sat, Mar 24, 2001 at 11:14:20PM -0500, Branden Robinson wrote: > On Sat, Mar 24, 2001 at 09:00:51PM -0500, Zephaniah E. Hull wrote: > > The 4 mesa packages are obvious, they will conflict, provide, and > > replace their counterparts[1]. > > > > Now, xserver-dri is a little less obvious, it depends on > > xserver-xfree86, but also needs to override 14 files[2] from it. > > I see superscripts but no footnotes. See my reply to Marcelo E. Magallon for said footnotes. Also, what he pointed out for the X server should work, not sure why I did not remember that. Zephaniah E. Hull. > > -- > G. Branden Robinson |Never underestimate the power of human > Debian GNU/Linux|stupidity. > [EMAIL PROTECTED] |-- Robert Heinlein > http://www.debian.org/~branden/ | -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. Knghtbrd: Any suggestions on how to semi-easily make $55? Mercury: if you went and beat the crap out of some QL people I'm sure you'd get at least tenfold that from people expressing their gratitude ;> (my luck he takes that seriously hehe) Knghtbrd: This channel is logged.. [msg(Knghtbrd)] If you can provide transportation.. <=:] [Knghtbrd([EMAIL PROTECTED])] hahahaha PGP signature
CVS DRI packages.
I am currently about ready to start testing of .debs out of the DRI cvs tree. I have a rough naming scheme, and a list of exactly what files will to be overridden. My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. The 4 mesa packages are obvious, they will conflict, provide, and replace their counterparts[1]. Now, xserver-dri is a little less obvious, it depends on xserver-xfree86, but also needs to override 14 files[2] from it. Right now I'm undecided on how to do the override, calling dpkg-divert from the preinst and postrm would work, but seems to be more of a kludge. As soon as the name scheme is agreed on and we have figured out how to override those files I can start testing on the DRI packages. Zephaniah E. Hull. -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. "Microsoft is a cross between the Borg and the Ferengi. Unfortunately, they use Borg to do their marketing and Ferengi to do their programming." -- Simon Slavin in asr pgpZ7nCAARj7R.pgp Description: PGP signature
Re: CVS DRI packages.
On Sat, Mar 24, 2001 at 09:00:51PM -0500, Zephaniah E. Hull wrote: > The 4 mesa packages are obvious, they will conflict, provide, and > replace their counterparts[1]. > > Now, xserver-dri is a little less obvious, it depends on > xserver-xfree86, but also needs to override 14 files[2] from it. I see superscripts but no footnotes. -- G. Branden Robinson |Never underestimate the power of human Debian GNU/Linux|stupidity. [EMAIL PROTECTED] |-- Robert Heinlein http://www.debian.org/~branden/ | PGP signature
Re: CVS DRI packages.
>> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > It might be possible to get X to search a different module path first, > but all examples of that turn out to be very ugly in the config file, > I'll keep poking. Ah, yes, that's actually cleaner. For the X server, you could change the symlink in /etc/X11/X, given there's a nice debconf interface and all that. -- Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS DRI packages.
On Sun, Mar 25, 2001 at 05:15:09AM +0200, Marcelo E. Magallon wrote: > I'm sorry, I forgot one important bit. > > >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > > > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. > > You might want to provide > xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (or whatever > the actual path is), as every now and then the DRM modules in the > kernel get out of sync with the ones in CVS. That will be after I get the basics working, likely provided in the same manner as other sets of kernel models. Zephaniah E. Hull. > > -- > Marcelo -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. It's also your right to f*ck up your own version of Linux, but you're not getting close to mine. Linus PGP signature
Re: CVS DRI packages.
On Sun, Mar 25, 2001 at 05:10:47AM +0200, Marcelo E. Magallon wrote: > >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > > > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. > > I would drop the xlibosmesa packages. libOSMesa is a software only > client side off-screen rendering library. > > > The 4 mesa packages are obvious, they will conflict, provide, and > > replace their counterparts[1]. > > You forgot the footnotes. Ahh, yes, my mistake. 1: Just s/-dri//g to get their counterparts. 2: I'll append the list to the bottom of this message. > > > Right now I'm undecided on how to do the override, calling dpkg-divert > > from the preinst and postrm would work, but seems to be more of a kludge. > > Is there other way? I actually think it's safer that way. Using alternatives might work, but Branden would have to very explicitly support that. It might be possible to get X to search a different module path first, but all examples of that turn out to be very ugly in the config file, I'll keep poking. Hopefully Branden will have some ideas. Zephaniah E. Hull. > > -- > Marcelo usr/X11R6/bin/XFree86 usr/X11R6/lib/modules/drivers/ati_drv.o usr/X11R6/lib/modules/drivers/atimisc_drv.o usr/X11R6/lib/modules/drivers/glint_drv.o usr/X11R6/lib/modules/drivers/i810_drv.o usr/X11R6/lib/modules/drivers/mga_drv.o usr/X11R6/lib/modules/drivers/r128_drv.o usr/X11R6/lib/modules/drivers/radeon_drv.o usr/X11R6/lib/modules/drivers/tdfx_drv.o usr/X11R6/lib/modules/drivers/vga_drv.o usr/X11R6/lib/modules/extensions/libGLcore.a usr/X11R6/lib/modules/extensions/libdri.a usr/X11R6/lib/modules/extensions/libglx.a usr/X11R6/lib/modules/linux/libdrm.a -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. ``Who killed the server at the colo site?'' ``Weasel killed the server at the colo site'' ``Not me'' ``Then who?'' ``m2 killed the server at the colo site'' ... PGP signature
Re: CVS DRI packages.
I'm sorry, I forgot one important bit. >> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. You might want to provide xc/programs/Xserver/hw/xfree86/os-support/linux/drm/kernel (or whatever the actual path is), as every now and then the DRM modules in the kernel get out of sync with the ones in CVS. -- Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: CVS DRI packages.
>> "Zephaniah E. Hull" <[EMAIL PROTECTED]> writes: > My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, > xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. I would drop the xlibosmesa packages. libOSMesa is a software only client side off-screen rendering library. > The 4 mesa packages are obvious, they will conflict, provide, and > replace their counterparts[1]. You forgot the footnotes. > Right now I'm undecided on how to do the override, calling dpkg-divert > from the preinst and postrm would work, but seems to be more of a kludge. Is there other way? I actually think it's safer that way. -- Marcelo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
CVS DRI packages.
I am currently about ready to start testing of .debs out of the DRI cvs tree. I have a rough naming scheme, and a list of exactly what files will to be overridden. My rough naming scheme is as follows: xlibmesa3-dri, xlibmesa-dri-dev, xlibosmesa3-dri, xlibosmesa-dri-dev, and xserver-dri. The 4 mesa packages are obvious, they will conflict, provide, and replace their counterparts[1]. Now, xserver-dri is a little less obvious, it depends on xserver-xfree86, but also needs to override 14 files[2] from it. Right now I'm undecided on how to do the override, calling dpkg-divert from the preinst and postrm would work, but seems to be more of a kludge. As soon as the name scheme is agreed on and we have figured out how to override those files I can start testing on the DRI packages. Zephaniah E. Hull. -- PGP EA5198D1-Zephaniah E. Hull <[EMAIL PROTECTED]>-GPG E65A7801 Keys available at http://whitestar.soark.net/~warp/public_keys. CCs of replies from mailing lists are encouraged. "Microsoft is a cross between the Borg and the Ferengi. Unfortunately, they use Borg to do their marketing and Ferengi to do their programming." -- Simon Slavin in asr PGP signature
