From: Phil Blundell <philb@gnu.org>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH 3/3] base-files-3.0.14 configuration files
Date: Mon, 21 Mar 2011 11:54:42 +0000 [thread overview]
Message-ID: <1300708482.2228.67.camel@phil-desktop> (raw)
In-Reply-To: <201103211236.39719.pgsellmann@portner-elektronik.at>
On Mon, 2011-03-21 at 12:36 +0100, Peter Gsellmann wrote:
> setting ONLINE_PACKAGE_MANAGEMENT = "none" precludes the use of CONFFILES_* in all recipes??
It doesn't preclude it, but it does render CONFFILES fairly useless.
It looks like the CONFFILES_micro = "" in this particular recipe was
added by me in 2b4ab236. I guess I probably did this to avoid having
nonexistent files show up in CONFFILES (since micro doesn't ship stuff
like motd at all). I don't recall whether I did this just for neatness
or whether OE was actually issuing a diagnostic for that situation.
I guess it might make some sense to just set CONFFILES_micro = ""
globally in micro.conf rather than doing it in individual recipes.
> As i can see, ONLINE_PACKAGE_MANAGEMENT is misused for micro image.
What do you mean?
p.
next prev parent reply other threads:[~2011-03-21 11:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-17 10:54 [PATCH 3/3] base-files-3.0.14 configuration files Peter Gsellmann
2011-03-17 11:10 ` Phil Blundell
2011-03-17 12:53 ` Hauser, Wolfgang (external)
2011-03-17 15:54 ` Peter Gsellmann
2011-03-18 8:59 ` Hauser, Wolfgang (external)
2011-03-18 10:56 ` Phil Blundell
2011-03-21 9:11 ` Hauser, Wolfgang (external)
2011-03-18 13:08 ` Peter Gsellmann
2011-03-18 15:30 ` Martin Jansa
2011-03-18 17:37 ` Peter Gsellmann
2011-03-21 9:30 ` Martin Jansa
2011-03-21 11:36 ` Peter Gsellmann
2011-03-21 11:54 ` Phil Blundell [this message]
2011-03-21 12:33 ` Peter Gsellmann
2011-03-21 13:58 ` Phil Blundell
2011-03-21 14:18 ` Peter Gsellmann
2011-03-21 12:53 ` [PATCH v2] " Peter Gsellmann
2011-03-21 16:39 ` Phil Blundell
2011-03-21 18:19 ` Peter Gsellmann
2011-03-22 11:17 ` [PATCH v3] " Peter Gsellmann
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=1300708482.2228.67.camel@phil-desktop \
--to=philb@gnu.org \
--cc=openembedded-devel@lists.openembedded.org \
/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.