Hi! I'm not too happy with the naming of packages right now:
dkms-nvidia: kernel module package nvidia-xorg: X11 driver and tools libnvidia-xorg1: shared libraries for i586 lib64nvidia-xorg1: shared libraries for x86_64 libnvidia-xorg1-devel: static libraries and headers for i586 lib64nvidia-xorg1-devel: static libraries and headers for x86_64 dkms-ati: kernel module package ati-xorg: X11 driver and tools ati-xorg-32bit-compat: x86 compatibility for x86_64 ati-devel: static libs and headers There are a few problems with this: If the x86_64 user wishes to use some x86 OpenGL software, either from the Mandriva i586 repository or 3rd party, he needs to have another pkg (libnvidia-xorg1, ati-xorg-32bit-compat) installed to have hardware 3D acceleration. - although explained in the description, this is not immediately obvious - also, since the recent separating of i586 and x86_64 repos on PLF, libnvidia-xorg1 is on i586 media, which the user may or may not have installed on x86_64 - this is incompatible with the Mandriva Club packages, that provide all the necessary libraries in the main package. Thus when user upgrades to PLF ones, he loses x86 3D acceleration support The naming "nvidia-xorg" and "ati-xorg" doesn't sound too logical, either. I have two different proposals: dkms-nvidia: kernel module package nvidia: X11 driver, tools and libraries nvidia-devel: static libs and headers dkms-ati: kernel module package ati: X11 driver, tools and libraries ati-devel: static libs and headers This is also the scheme that Mandriva's Club packages use, and is pretty simple. In this scheme, the libs, including 32bit compatibility libs would be embedded in the main package. Thus "nvidia" would be 2MB larger than the previous "nvidia-xorg", and "ati" would be 5MB larger than the previous "ati-xorg". The other one: nvidia: metapackage requiring everything dkms-nvidia: kernel module package x11-driver-video-nvidia: X11 driver, tools and libraries nvidia-gl: GL libraries nvidia-gl-32bit-compat: 32bit GL libraries for x86_64 nvidia-devel: static libs and headers ati: metapackage requiring everything dkms-ati: kernel module package x11-driver-video-fglrx: X11 driver, tools and libraries ati-gl: GL libraries ati-gl-32bit-compat: 32bit GL libraries for x86_64 ati-devel: static libs and headers (the control panel could also be separated, as it requires qt3 etc) Here Club compatibility is also preserved, but we have split the pkg to smaller chunks. This allows the user to (1) not install 32bit-compat if he doesn't want to and (2) install a driver without the hardware 3d stuff. People, please tell me what would you prefer? I like the first one (Club scheme) more, as IMHO the latter one is too complicated for very little gain. If you have something else to suggest, please do so. -- Anssi Hannula _______________________________________________ PLF-discuss mailing list [email protected] https://www.zarb.org/mailman/listinfo/plf-discuss
