ports/105135: net/linux-nx-client: update to 2.1.0
Eric P. Scott
eps+pbug0611 at ana.com
Sun Nov 5 22:00:48 UTC 2006
The following reply was made to PR ports/105135; it has been noted by GNATS.
From: "Eric P. Scott" <eps+pbug0611 at ana.com>
To: bug-followup at freebsd.org
Cc:
Subject: Re: ports/105135: net/linux-nx-client: update to 2.1.0
Date: Sun, 5 Nov 2006 13:52:01 -0800 (PST)
This still isn't quite right; I see it's running FreeBSD's
ldconfig instead of the Linux one. BTW, the reason it appears to
work anyway is nxclient sets LD_LIBRARY_PATH for its
subprocesses.
I tried adding the "obviously missing" USE_LINUX_PREFIX= yes to
the Makefile, but that didn't seem to help; it appears I really
do need INSTALLS_SHLIB. That causes the correct ldconfig to be
used, but it can't see the package's shared libraries, since
they're under the wrong root. I think I want
NXDST= [something like]
${LINUXBASE}/usr/X11R6/lib/linux-nx-client
-and-
create a ${LINUXBASE}/etc/ld.so.conf.d/linux-nx-client.conf
containing
/usr/X11R6/lib/linux-nx-client/lib
so the Linux ldconfig will add it to the ld.so cache.
[Make appropriate changes to pkg-plist.]
"This isn't how I would have done things"
There's a brief section in the Porter's Handbook (12.13) titled
"Do things rationally." I'm questioning whether there's still
a need (or even a good justification) for sticking things under
${X11BASE}/lib/linux-nx-client at all. Why not simply install
the necessary [i.e. non-conflicting] Linuxy bits under
${LINUXBASE}/usr/NX/{bin,lib,share} so it looks more like a
"normal" NX installation? Then the only "argument" to settle is
whether the FreeBSD-specific shell scripts properly belong under
${X11BASE} or ${LOCALBASE}.
(No, I am not interested in taking over maintainership of this
port ... it's giving me a headache. I still don't have a good
suggestion for how to handle nxprint's libcups.so.2 dependency.
I certainly don't want a hard requirement for print/cups-base.
I don't consider lack of printing capability a show-stopper.)
It's time for me to hand this off to someone else. Volunteers?
More information about the freebsd-ports-bugs
mailing list