All of lore.kernel.org
 help / color / mirror / Atom feed
From: Koen Kooi <k.kooi@student.utwente.nl>
To: openembedded-devel@openembedded.org
Cc: opkg-devel <opkg-devel@googlegroups.com>
Subject: Re: [RFC] opkg conffiles force overwrite
Date: Fri, 03 Apr 2009 06:16:19 +0200	[thread overview]
Message-ID: <49D58D93.20803@student.utwente.nl> (raw)
In-Reply-To: <6b7bf6e9-f3cb-4460-b1dc-312bc0ced19e@j18g2000prm.googlegroups.com>

On 03-04-09 05:59, Tick wrote:
> Hi All,
>    I am pondering that let conf->force_overwrite in opkg enable
> resolve_conffiles overwrite any conffiles. Now opkg will not overwrite
> the conffiles even if you set force_overwrite. It will cause opkg ask
> user to choose what to do to the conffiles if they are changed.
>
> Adding another flag e.g. force_overwrite_conffile seems a little bit
> superfluous and not orthogonal to force_overwrite. But it will not
> change current opkg behavior.
>
> Letting force_overwrite can overwrite conffiles will cause logical
> change of this flag.  This will make opkg-cl asking nothing when
> upgrade some conffiles if you set force_overwrite. It may cause users
> lose their own setting without a second chance to save them?
>
> In my own opinion, I prefer let force_overwrite flag can overwrite
> files including conffiles, because it has to be set manually. But this
> will change the behaviour of opkg, and may have some impact on other
> projects. Such as OE. That makes me consider again and again.
>
> My proposal is if conffiles been overwrited because force_overwrite
> was set.
> The old conffile XXXX will be move to XXXX~, and adding a warning
> message of "overwriting conffile XXXX".
> Is that a good solution?

It's not a good solution since people use 'force-overwrite' to get 
around packages that don't (or can't) have RREPLACES set. If I do an 
opkg upgrade now, I don't want util-linux-ng-mount and busybox to start 
fighting over /etc/mountall, but I do want opkg to prompt me about fstab 
changes.

regards,

Koen



  reply	other threads:[~2009-04-03  4:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-04-03  3:59 [RFC] opkg conffiles force overwrite Tick
2009-04-03  4:16 ` Koen Kooi [this message]
2009-04-03  4:46 ` Angus Ainslie

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=49D58D93.20803@student.utwente.nl \
    --to=k.kooi@student.utwente.nl \
    --cc=openembedded-devel@lists.openembedded.org \
    --cc=openembedded-devel@openembedded.org \
    --cc=opkg-devel@googlegroups.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.