Hi, Le mercredi 13 août 2014 à 12:10 +0100, Simon Kelley a écrit : > I worry that it's an unfriendly thing to do to make a upgrade break any > existing installation that uses a file in /etc/dnsmasq.d that doesn't > end in .conf. I guess that the postinst script could check for this, and > generate a warning, or configure differently if such files already exist.
It is indeed not very friendly, but if correctly advertised, it should be OK. That is what module-init-tools did (also renaming conffiles installed by itself, I think). > My though for config-dir would be to allow something like > > --config-dir=/etc/dnsmasq.d,\*.conf BTW, do you intend to change it to --config-dir or is it a typo? > ie the arguments are the directory (as now) followed by one or more > file-endings to exclude (as now) and one or more file endings to > include, marked by preceding them with *. * is a problem on the command > line, because it's a shell metacharacter, but it make the meaning very > obvious. Well, this wouldn't look so obvious to a newcomer, I think (just prepending a * to mean the opposite?…) but I can't find a better idea while keeping the same option (and keeping it backward compatible, as switching to --conf-dir suffix list to mean “include” instead of exclude would be easier, and having to exclude by prepending e.g. “!”). Regards, -- Benjamin Cama <[email protected]> -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
