openembedded-core.git/meta/conf/layer.conf, branch 2015-4 Mirror of openembedded-core layer.conf: bump version as error-report interface changed 2015-03-10T17:44:56+00:00 Ross Burton ross.burton@intel.com 2015-03-10T16:28:08+00:00 99f209a49a4390192b95184ff86bd6f973010111 The error-report tooling command-line options were changed and anyone doing automated builds and using error-reports needs to know what options to parse. Signed-off-by: Ross Burton <ross.burton@intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
The error-report tooling command-line options were changed and anyone doing
automated builds and using error-reports needs to know what options to parse.

Signed-off-by: Ross Burton <ross.burton@intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
layer.conf: set a variable to map to the OE Layer Index name 2015-02-21T22:04:26+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2015-02-20T17:44:06+00:00 d1cf0edd79ec3ba3bd17126183e4cb99aa50ffaf Add a variable that allows us to map the OE-Core layer to the name that represents it in the OpenEmbedded layer index. This will be used by bitbake-layers layerindex-fetch so that it knows that for example OE-Core is already fetched and included in the current configuration. Note - it won't be required for us to go around and set this for every layer - we can do the matching based on repo and subdirectory, but OE-Core is somewhat special in that it does sometimes appear in different places, for example in poky. [YOCTO #5348] Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Add a variable that allows us to map the OE-Core layer to the name that
represents it in the OpenEmbedded layer index. This will be used by
bitbake-layers layerindex-fetch so that it knows that for example
OE-Core is already fetched and included in the current configuration.

Note - it won't be required for us to go around and set this for every
layer - we can do the matching based on repo and subdirectory, but
OE-Core is somewhat special in that it does sometimes appear in
different places, for example in poky.

[YOCTO #5348]

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
opkg-arch-config: Renamed from opkg-config-base 2015-02-03T14:53:44+00:00 Paul Barker paul@paulbarker.me.uk 2014-12-19T17:31:16+00:00 d0cb4fb3aab1d6041f88fa564e5d745629316ae2 The name 'opkg-arch-config' is much more descriptive. Signed-off-by: Paul Barker <paul@paulbarker.me.uk> 
The name 'opkg-arch-config' is much more descriptive.

Signed-off-by: Paul Barker <paul@paulbarker.me.uk>
layer.conf: Mark opkg-utils as ABISAFE for update-alternatives usage 2014-09-23T20:38:47+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-09-23T19:01:01+00:00 6829c0e161c4a8cde6624f211865922fce62d4fa Currently linux-firmware rebuilds for each machine due to its usage of update-alternatives which in turn means a dependency on opkg-utils. Marking opkg-utils as ABISAFE is the only option we have right now to avoid this. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Currently linux-firmware rebuilds for each machine due to its usage of
update-alternatives which in turn means a dependency on opkg-utils.
Marking opkg-utils as ABISAFE is the only option we have right now
to avoid this.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
layer.conf: Add in useradd dependencies as ABISAFE dependencies 2014-09-23T20:38:47+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-09-23T19:01:28+00:00 7743a309017f0fb9286f00b1f6f546ee95c05303 Currently allarch recipes using useradd rebuild each time MACHINE changes which is not desireable. Adding the useradd dependencies to this list ensures they do not change under these circumstances. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Currently allarch recipes using useradd rebuild each time MACHINE
changes which is not desireable. Adding the useradd dependencies
to this list ensures they do not change under these circumstances.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
conf: Account for eglibc->glibc move 2014-09-01T17:00:31+00:00 Khem Raj raj.khem@gmail.com 2014-08-28T06:10:13+00:00 bbd2eae187f9d6cadf03cbe8d84259593e3551ce Change references in documentation appropriately Signed-off-by: Khem Raj <raj.khem@gmail.com> 
Change references in documentation appropriately

Signed-off-by: Khem Raj <raj.khem@gmail.com>
SIGGEN_EXCLUDERECIPES_ABISAFE: add initscripts 2014-08-11T16:44:09+00:00 Martin Jansa martin.jansa@gmail.com 2014-08-11T14:09:13+00:00 4321c553d5ae816e566234e981a0815bba046d39 * update-rc.d now adds initscripts dependency even to allarch recipes making them effectively TUNE_PKGARCH, "fix" it by excluding initscripts from all signatures Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
* update-rc.d now adds initscripts dependency even to allarch recipes
  making them effectively TUNE_PKGARCH, "fix" it by excluding
  initscripts from all signatures

Signed-off-by: Martin Jansa <Martin.Jansa@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
layer.conf: Add musl to safe recipes for exclusion 2014-05-30T15:31:22+00:00 Khem Raj raj.khem@gmail.com 2014-05-29T07:01:07+00:00 ad8ccccf442e29a0b733753c1951f402baa330a9 Signed-off-by: Khem Raj <raj.khem@gmail.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
Signed-off-by: Khem Raj <raj.khem@gmail.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
layer.conf: Exclude gcc-cross dependencies from checksums 2014-05-01T21:49:00+00:00 Richard Purdie richard.purdie@linuxfoundation.org 2014-05-01T14:40:40+00:00 97df4e8e61a7693d548c3145e36f1d5503e91d03 gcc-cross technically depends on the C library however we can use one toolchain for multiple different tunes within a given architecture. Manually remove these dependencies so that gcc-cross isn't rebuild with every tune change. Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
gcc-cross technically depends on the C library however we can use
one toolchain for multiple different tunes within a given architecture.

Manually remove these dependencies so that gcc-cross isn't rebuild with
every tune change.

Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
layer.conf: update LAYERVERSION_core for core-image-full-cmdline 2014-03-07T14:44:25+00:00 Paul Eggleton paul.eggleton@linux.intel.com 2014-03-07T10:23:44+00:00 d87585385bfe00dd5e7448ae7d5bc5dc7f9ac782 LAYERVERSION_core change to 4 means rename of core-image-basic to core-image-full-cmdline. Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com> Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org> 
LAYERVERSION_core change to 4 means rename of core-image-basic to
core-image-full-cmdline.

Signed-off-by: Paul Eggleton <paul.eggleton@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>