* Updating configuration files, how to
@ 2016-03-10 9:15 Jaap de Jong
2016-03-10 9:37 ` Gary Thomas
0 siblings, 1 reply; 3+ messages in thread
From: Jaap de Jong @ 2016-03-10 9:15 UTC (permalink / raw)
To: openembedded-devel@lists.openembedded.org
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?
Thanks in advance!
Jaap
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Updating configuration files, how to
2016-03-10 9:15 Updating configuration files, how to Jaap de Jong
@ 2016-03-10 9:37 ` Gary Thomas
2016-03-10 19:51 ` Paul Eggleton
0 siblings, 1 reply; 3+ messages in thread
From: Gary Thomas @ 2016-03-10 9:37 UTC (permalink / raw)
To: openembedded-devel
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
------------------------------------------------------------
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: Updating configuration files, how to
2016-03-10 9:37 ` Gary Thomas
@ 2016-03-10 19:51 ` Paul Eggleton
0 siblings, 0 replies; 3+ messages in thread
From: Paul Eggleton @ 2016-03-10 19:51 UTC (permalink / raw)
To: Jaap de Jong; +Cc: openembedded-devel, Gary Thomas
On Thu, 10 Mar 2016 10:37:10 Gary Thomas wrote:
> On 2016-03-10 10:15, Jaap de Jong wrote:
> > 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).
FYI in recent versions (jethro / 2.0+) you can use "recipetool appendfile" to
create these bbappends easily. You don't even have to know which recipe is
packaging them.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2016-03-10 19:51 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2016-03-10 9:15 Updating configuration files, how to Jaap de Jong
2016-03-10 9:37 ` Gary Thomas
2016-03-10 19:51 ` Paul Eggleton
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.