Move the configuration files /etc/libnss-mysql.cfg and /etc/libnss-mysql-root.cfg to /etc/libnss-mysql/ Makes it look cleaner, especially since there are more than one configuration file. The patch for the ebuild is easy just add: src_compile() { econf --sysconfdir=/etc/libnss-mysql emake } Tested it and works like a charm.. Reproducible: Always Steps to Reproduce: 1. 2. 3.
I don't really see the point of having /etc/libnss-mysql/libnss-mysql.cfg...seems redundant...and it's only two conf files. Is this really necessary? Besides, this change will break current installations, which is something to avoid...
Created attachment 28316 [details, diff] libnss-mysql-1.1.ebuild.diff This patch adds support for "/etc/libnss-mysql"-directory w/o breaking backward compability. Further default config-files are added as /etc/libnss-mysql/*.dist, this is more like the behavior for e.g. portage where /etc/make.conf.dist is now provided rather than /etc/make.conf.
I still don't think this is necessary. I haven't heard a good argument as to why these two files should be in their own directory. What is the point? This just adds clutter to the ebuild for not much gain.
Well, first of all it is cleaner for the admins and the extra cludge to the ebuild can be removed over time (this is just to make a transition smooth for those admins that don't look over the ChangeLog file before installing mission critical applications/librarys). I think it is about beeing persistent about packages that have more than one configuration file, like samba, apache, cups, openssl, php, syslog-ng .. and so on and so on.. and it looks better :) and it is easier to put a sample configuration file right there with it.. without cludging up /etc .. it is more structured .. it is any sys-admins wet dream? :) I think there is a Gentoo policy somewhere for it, but I havn't been able to locate it, maybe my mind is just pulling tricks on me..
sorry, I'm not convinced this is necessary. It's two simple files.
