On Tue, Mar 02, 2010 at 02:41:56PM +0100, Adrian Knoth wrote:
On Mon, Mar 01, 2010 at 07:42:25PM -0300, Felipe Sateler wrote:

> +    mv $CONFIG_FILE{,.disabled} || true
Note that the {,} idiom is a bashism. It will fail with dash as /bin/sh

Thanks, that's fixed.

From a quick glance it looks to me that you are moving around a conffile in a packaging script. It is tricky to do so properly - an example of what might else happen is users getting confusing questions if they want to preserve or overwrite "their" changes at package update.

When switching from non-confile to conffile (which seems to be the case here) there are (complex) ways to handle that properly by using ucf instead and hashing the older default config files.

Tell me if it would be relevant to dust off an old example of doing that (from the uw-imap package some years ago when it contained a configfile).

 - Jonas

* Jonas Smedegaard - idealist & Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 [x] quote me freely  [ ] ask before reusing  [ ] keep private

Attachment: signature.asc
Description: Digital signature

pkg-multimedia-maintainers mailing list

Reply via email to