Re: [oe] Updating configuration files, how to

2016-03-10 Thread Paul Eggleton
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
-- 
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel


Re: [oe] Updating configuration files, how to

2016-03-10 Thread Gary Thomas

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

--
___
Openembedded-devel mailing list
Openembedded-devel@lists.openembedded.org
http://lists.openembedded.org/mailman/listinfo/openembedded-devel