From: Gary Thomas <gary@mlbassoc.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Updating configuration files, how to
Date: Thu, 10 Mar 2016 10:37:10 +0100 [thread overview]
Message-ID: <56E14046.8090203@mlbassoc.com> (raw)
In-Reply-To: <56E13B20.8010902@nedap.com>
On 2016-03-10 10:15, Jaap de Jong wrote:
> Hi All,
>
> I am wondering what the best approach is for creating 'standard' packages with updated configuration files.
> As an example: I want to have a package with an updated /etc/network/interfaces file to reflect my systems hardware.
> Should I create a init-ifupdown_1.0.bbappend recipe with the updated file?
> What other options do I have?
> What are you guys using for this?
> And how about the package name in such a case. Append something to its name?
I use a init-ifupdown_1.0.bbappend in my target machine (BSP) layer,
this way these settings only affect the particular machine(s).
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2016-03-10 9:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-10 9:15 Updating configuration files, how to Jaap de Jong
2016-03-10 9:37 ` Gary Thomas [this message]
2016-03-10 19:51 ` Paul Eggleton
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=56E14046.8090203@mlbassoc.com \
--to=gary@mlbassoc.com \
--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.