From: Angus Ainslie <nytowl@openmoko.org>
To: openembedded-devel@lists.openembedded.org
Cc: opkg-devel <opkg-devel@googlegroups.com>
Subject: Re: [RFC] opkg conffiles force overwrite
Date: Thu, 02 Apr 2009 22:46:37 -0600 [thread overview]
Message-ID: <1238733997.6527.26.camel@think-laptop> (raw)
In-Reply-To: <6b7bf6e9-f3cb-4460-b1dc-312bc0ced19e@j18g2000prm.googlegroups.com>
On Thu, 2009-04-02 at 20:59 -0700, Tick wrote:
> 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.
There is currently a force-defaults switch so why not have a
force-maintainer or something similar. In OE specifically it would be
nice to be able to set this per recipe to try and guarantee a certain
config. The problem comes when 2 different recipes try to assert them
selves by using th force-maintainer flag.
Angus
prev parent reply other threads:[~2009-04-03 4:49 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
2009-04-03 4:46 ` Angus Ainslie [this message]
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=1238733997.6527.26.camel@think-laptop \
--to=nytowl@openmoko.org \
--cc=openembedded-devel@lists.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.