2019-01-16 16:54 CET

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0005119GNUnetGNSpublic2018-06-04 18:43
Assigned Tong0 
PrioritynormalSeverityminorReproducibilityhave not tried
Product Version 
Target VersionFixed in Version 
Summary0005119: followup to 0005078 / GNS library file changes
DescriptionI was just informed that https://gnunet.org/bugs/view.php?id=5078 was solved by:

> Users / distros now must manually move the $PREFIX/lib/gnunet/nss/* files to the respective directory where libc expects NSS plugins (or adjust the search path).

This is bad in practice. There is no notice about this, no message. And even if you are expected to read something as a package maintainer (as in package in distro) you are likely to miss it.
The best is to to assume no interaction.
So what's the best way to solve this? I can simply adjust this on my system and the package, that's not a problem.
There should be a configure time option to select the directory for this.
TagsNo tags attached.
Attached Files

-Relationships Relation Graph ] Dependency Graph ]



Christian Grothoff (manager)

The big issue here is that this is not so much about installing the plugin in the NSS directory. The bigger required change (for the user) is to activate it by editing /etc/nsswitch.conf. Doing that is a big decision, so it should only be done by a package maintainer or end-user who knows what they are doing (and how to revert).


ng0 (developer)

/etc/nssswitch.conf is no problem in my opinion.
What bothers me more is expected manual intervention for lib/gnunet/nss/* ... the nssswitch.conf can be installed (it is now in contrib/conf/nss/) as "example" data under share/gnunet/nss/$file.
It's not problem to adjust and extend the nss search-path, but we should communicate it. 9 out of 10 package maintainers will probably not get it if we simply write it in the manual. And for those who skip the README file, we can make an output on the screen ("for nss support, do...") after make has finished.

That's how I would resolve this issue for now.



Christian Grothoff (manager)

Having a configure option still means maintainers could miss it. But feel free to add it, as long as not setting it doesn't break the build.

-Issue History
Date Modified Username Field Change
2017-08-17 18:35 ng0 New Issue
2018-04-01 15:52 Christian Grothoff Note Added: 0012912
2018-05-22 12:49 ng0 Note Added: 0012941
2018-05-22 12:50 ng0 Assigned To => ng0
2018-05-22 12:50 ng0 Status new => assigned
2018-06-04 18:43 Christian Grothoff Note Added: 0012979
+Issue History