On Fri, Mar 2, 2012 at 11:02 AM, Konstantin Belousov <kostik...@gmail.com> wrote: > On Fri, Mar 02, 2012 at 10:54:46AM -0800, Freddie Cash wrote: >> On Fri, Mar 2, 2012 at 10:49 AM, Konstantin Belousov >> <kostik...@gmail.com> wrote: >> > And yes, I use a script that checks PCI devices on boot and symlinks >> > libGL.so.1 and libglx.so to appropriate implementations. The only trouble >> > right now is that reinstall of libGL or nvidia driver ports requires >> > manual fixing of the .so. >> >> Ah, but splitting the GL bits out into slave ports would fix that. :) > > No, it moves the moment of problem from mesa/nvidia update to mesa-libGL > and nvidia-libGL update. And, libGl.so.1 from Mesa is already in the > separate port, FWIW.
How? Unless the ports include the creation of the symlink (which they shouldn't), then there is no problem anymore. You install nvidia-gl port, you get libGL-nvidia.so installed. You install mesa-gl port, you get libGL-mesa.so installed. You run the "alternatives" script to create the symlink (or manually create it, or tweak a knob somewhere to create it), and then never touch it again. Update nvidia-gl port, only libGL-nvidia.so gets updated. The symlink doesn't change. Update mesa-gl port, only libGL-mesa.so gets updated. The symlink doesn't change. Where's the problem? -- Freddie Cash fjwc...@gmail.com _______________________________________________ freebsd-ports@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-ports To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"