J.A. Magallón wrote:
> Hi all...
Hi!
> I have been trying to build a package for new nvidia drivers, starting from
> the current packages in cooker. Apart from the results, I have noticed some
> things:
>
> - The src.rpm package (nvidia-current-185.18.36-4mdv2010.0.src.rpm)
> includes this files from nvidia:
> NVIDIA-Linux-x86-185.18.36-pkg0.run
> NVIDIA-Linux-x86_64-185.18.36-pkg2.run
> Why 'pkg2' for x86.64 ? Using pkg0 will save bout 8Mb in the src.rpm...
> Or is there something in that package that is not in pkg0 ?
From nvidia-current.spec:
# pkg0: plain archive
# pkg1: + precompiled modules
# pkg2: + 32bit compatibility libraries
on 64-bit we need the 32bit compatibility libraries.
> - x11-driver-video-nvidia-current for x86-64 includes a bunch of 32bit
> libraries in /usr/lib/nvidia-current. Why ? Shouldn't you install the
> 32 bit package if you want 32 bit compatibility ?
I don't want to split the package like that, as I think there'd be many
people who want 32-bit compatibility but don't know they need to install
some separate package for that. They only get software 3d acceleration
and then just try the official nvidia drivers, which then break on
upgrades and problems ensue.
Of course, if people universally disagree with me, I'm ready to change that.
> - nvidia-current-devel also includes 32bit links in /usr/lib/nvidia-current
>
> Now that even CUDA 2.3 provides a 64bit profiler, one can have a pure 64bit
> nvidia system ;) There should not be any /usr/lib/nvidia-current directory
> on a 64 bit system, I think, nor include /usr/lib/nvidia-current in ld.so.conf.
>
> Is there something I don't see ?
See above. Note that the 32-bit libraries' dependencies are not
considered, so you can freely remove all their dependencies from your
system.
BTW, removing /usr/lib/nvidia-current from ld.so.conf is not easily
possible at all (we can't automatically add it when 32-bit compat lib
package would be installed).
--
Anssi Hannula
