[x11/nvidia-driver] conflicts with linux dri ports
mel.flynn+fbsd.ports at mailing.thruhere.net
Thu Jun 11 18:58:32 UTC 2009
On Sunday 07 June 2009 16:00:37 RW wrote:
> On Mon, 08 Jun 2009 00:06:56 +0400
> Boris Samorodov <bsam at ipt.ru> wrote:
> > On Sun, 7 Jun 2009 21:34:53 +0200 barbara wrote:
> > > > I've just received a report at emulation@ about x11/nvidia-driver
> > > > and other linux dri ports to be in conflict.
> > > >
> > > > If a linux dri port is installed x11/nvidia-driver seems to
> > > > replace libGL.so with a link to nvidia library. Not good. Is it
> > > > right to mark this port and other linux dri ports to be in
> > > > conflict?
> > >
> > > Why it's not good?
> > > I'm not sure I've understood, but I think it's more or less the
> > > same with the native counterpart: if you install x11/nvidia-driver,
> > > libGL.so from graphics/libGL get replaced (actually renamed).
> > Because if port B replaces a file from port A, then when port A is
> > deinstalled, the file from the ports B is removed.
> It's not ideal, but making nvidia-driver conflict with its own
> dependencies is a lot worse.
nvidia-driver's dependency on libGL is artificial (cause it needs to replace
libGL, not cause it needs to link with it). One can actually build and install
the driver without having libGL from ports installed.
As such I've tried decoupling this a year or so ago, but aside from some
problems in the nvidia-provided Makefiles that I could patch, the major
drawback of it was that every port requiring libGL would now have to be taught
about nvidia-driver (Yes, bsd.gl.mk but there were a few exceptions).
I ran into one major hurdle, but can't for the life of me remember anymore
what it was, so decided to back off and live with the current hacks.
I could try again and at least see what the problem is, in a week or two at
the earliest. What I was aiming for is:
- if defined(WITH_NVIDIA_GL) libdep on nvidia-driver else libGL
- no more XXX-files and post-install hacks
- no more "need xorg-server installed before we can even read our Makefile"
Vague memories surfacing: problem had to do with either compat5x or linux.
More information about the freebsd-ports