[prev in list] [next in list] [prev in thread] [next in thread] 

List:       busybox
Subject:    Re: [PATCH v4] dpkg: no config file overwrite
From:       Denys Vlasenko <vda.linux () googlemail ! com>
Date:       2010-03-29 12:21:41
Message-ID: 1158166a1003290521r59341416k74d3c1549aa7af3e () mail ! gmail ! com
[Download RAW message or body]

On Wed, Mar 24, 2010 at 2:15 PM, Kim B. Heino <Kim.Heino@bluegiga.com> wrote:
> This patch changes how dpkg handles config files. There are three modes:
>
> 1) If config file is unchanged by user then it will be overwritten. If
> changed, then new config file will be created as configfile.dpkg-new.
> This is how "real dpkg" handles config files. This is the default mode.
>
> 2) Parameter --force-confnew. Always overwrite config files.
>
> 3) Parameter --force-confold. Never overwrite, always create .dpkg-new.
>
>
> Changes for v4:
> - Long --force-confxxx options instead of non-compatible short ones.
> - Add long options for --install, --list, etc.
>
> Changes for v3:
> - "Changed by user?" -check added.
> - -N and -O options added.
> - Not a config option anymore (because of new default mode).
>
>
> Comments needed:
>
>> In the long run, pain from having noncompatible behavior
>> is worse than pain from one-time conversion for the users
>> which depend on current behavior.
>
> What should we do about -C, -F and -u if LONG_OPTS is not enabled? Real
> dpkg does not have any short options for them.

With longopts off,
perhaps we should not provide colliding options (like -C)
but may still have some bbox-specific ones.

With longopts on, I prefer to be as compatible as possible.

Applied with some editing.

Please test (I mean it!) current git.

Thanks!

-- 
vda
_______________________________________________
busybox mailing list
busybox@busybox.net
http://lists.busybox.net/mailman/listinfo/busybox
[prev in list] [next in list] [prev in thread] [next in thread]