After some more discussion with Bertrand, I've committed a patch to SVN
HEAD (SVN 24295) which allows the user to control NSS library
installation. There are a few possibilities:
1) If configure is run by root or using the '--with-sudo' option, NSS
plugins are by default installed to "/lib" (sane default for normal users)
2) If configure is run by a normal user and without the '--with-sudo'
option, NSS plugins are by default not installed _at all_.
3) If configure is run "--with-nss=no", then NSS plugins are never installed
4) If configure is run "--with-nss=yes", then NSS plugins are always
installed to "/lib", even if neither '--with-sudo' is given nor
configure is run as root. Installation will fail unless 'make install'
is run as root.
5) If configure is run "--with-nss=$SOMEPATH", then NSS plugins are
always installed to $SOMEPATH. _This_ is likely the best option for
Debian packaging. You'd run like this:
./configure \
--prefix=/tmp/buildd/gnunet-0.9.X/debian/tmp/usr \
--with-nss=/tmp/buildd/gnunet-0.9.X/debian/tmp/lib
This way, most stuff will end up properly in
/tmp/buildd/gnunet-0.9.X/debian/tmp/usr/{lib,bin,share}
and NSS plugins in
/tmp/buildd/gnunet-0.9.X/debian/tmp/lib/
so when the /tmp/buildd/gnunet-0.9.X/debian/tmp/-prefix is mapped to '/'
by dpkg on install, all should be well.
Happy hacking!
Christian
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
