On Mon, 18 Nov 2013, Bill Allombert wrote: > > so checking/patching also a cron file although possible, might be a bit too > > much of a hack...
> Indeed, patching conffiles at install time is a big no-no. ;-) I know I know... (blushing) > > Looking forward though -- imho it would be nice if the > > /etc/popularity-contest.conf had at the end smth like > > if [ -d /etc/popularity-contest.d ]; then > > for i in /etc/popularity-contest.d/*.conf; do > > if [ -r $i ]; then > > . $i > > fi > > done > > unset i > > fi > > so we could avoid patching at all and just provide > > /etc/popularity-contest.d/neurodebian.conf which would extend the necessary > > variables? > The problem is that the result depends in which order the "for" loop read the > file, > since they all set the same variables, unless one do in all the *.conf like > SUBMITURLS="$SUBMITURLS http://myurl"; > so this is not very robust. as long as it is reasonably documented -- it is bullet-proof! ;) could also do smth like /bin/ls /etc/popularity-contest.d/*.conf | sort | while read i; do to provide consistency in order -- Yaroslav O. Halchenko, Ph.D. http://neuro.debian.net http://www.pymvpa.org http://www.fail2ban.org Senior Research Associate, Psychological and Brain Sciences Dept. Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
