<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/bitbake/bin/bitbake-layers, branch 1.3_M4</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=1.3_M4</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=1.3_M4'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2012-08-22T12:59:56+00:00</updated>
<entry>
<title>bitbake: bitbake-layers: use parsable title for show-appends</title>
<updated>2012-08-22T12:59:56+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-08-21T17:11:47+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=1426e14747d08f667bc921c6c3f1cc3187d0de47'/>
<id>urn:sha1:1426e14747d08f667bc921c6c3f1cc3187d0de47</id>
<content type='text'>
Print title text surrounded by === as we do with other subcommands so
that you can filter it out in scripts. (You will also want to filter out
lines starting with "WARNING:" if you just want the list).

(Bitbake rev: ba15ba16a5d863886bcfd5b3f0bdfff2a6de11a0)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-layers: avoid full parse for show-layers subcommand</title>
<updated>2012-08-22T12:59:56+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-08-21T17:11:46+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=5d09fb034625114a82eb198f5b69da6ed230cb29'/>
<id>urn:sha1:5d09fb034625114a82eb198f5b69da6ed230cb29</id>
<content type='text'>
We don't actually need to parse all recipes just to show the configured
layers, so just parse the configuration instead.

(Bitbake rev: 406477cbae066b6379873e266cb79801e545a61c)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake: bitbake-layers: fix help for show-overlayed to match behaviour</title>
<updated>2012-08-02T16:05:06+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-07-24T11:41:24+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=94f57a169e393f659184f1d7a4df01f175521c1e'/>
<id>urn:sha1:94f57a169e393f659184f1d7a4df01f175521c1e</id>
<content type='text'>
show-overlayed actually lists the same recipe in multiple layers
regardless of priority, so change the help description to match.

(Bitbake rev: 17217ff707e41780cb473b9cdd2621dd18b982c2)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake-layers: hide deprecation warnings</title>
<updated>2012-04-17T10:41:31+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-04-16T22:31:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=04d6aa1069f68562cc28167c4bf9f0096789ec7f'/>
<id>urn:sha1:04d6aa1069f68562cc28167c4bf9f0096789ec7f</id>
<content type='text'>
There are a number of DeprecationWarnings within BitBake code which
bitbake itself filters out; bitbake-layers was not doing this, resulting
in a stream of warnings printed out when used with Python &lt; 2.7 (these
warnings default to disabled on version 2.7 and above.)

(Bitbake rev: 0a2378237f07eb1c812e2308e64b7d70781e2b39)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake-layers: fix traceback in show-overlayed with nothing overlayed</title>
<updated>2012-03-20T15:21:32+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-03-19T11:18:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=30e35fa094d4ee75796f48b57d37b35cf73d935a'/>
<id>urn:sha1:30e35fa094d4ee75796f48b57d37b35cf73d935a</id>
<content type='text'>
There is no logger.note, use logger.plain instead (which is what we
really want here anyway.)

(Bitbake rev: c4f7fd708c48d4323db4bbeb3074f576f5be7aa2)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake-layers: add copyright notice</title>
<updated>2012-02-09T14:14:20+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-01-30T16:25:49+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=8d41b0ddbf02fcd8b44f36f59194d5a9c2292092'/>
<id>urn:sha1:8d41b0ddbf02fcd8b44f36f59194d5a9c2292092</id>
<content type='text'>
This ought to have been added earlier. (I consulted with Chris Larson on
the notice covering his work.)

(Bitbake rev: 69ed02b645bdc28c1bf24e436beeed37d226b56b)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake-layers: list overlayed classes in show-overlayed</title>
<updated>2012-02-01T15:08:42+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-01-30T16:25:54+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=90e99a5caefcfd53c9c2780382432df7550f2d2b'/>
<id>urn:sha1:90e99a5caefcfd53c9c2780382432df7550f2d2b</id>
<content type='text'>
Classes (.bbclass files) can be overlayed in a layer although they are
currently located by BitBake in a different way (via BBPATH instead of
using layer priority) and thus it is useful to be able to see when this
is in effect and which layer's class is actually being used.

(Bitbake rev: f6493e4bad005a82580380d800ebf4c438292f5b)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake-layers: add show-recipes subcommand</title>
<updated>2012-02-01T15:08:42+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-01-30T16:25:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=86a5fcd2c62585152fabc271b8e7893fe31399a9'/>
<id>urn:sha1:86a5fcd2c62585152fabc271b8e7893fe31399a9</id>
<content type='text'>
Add a show-recipes subcommand which lists all available recipes, with
the layer they are provided by. You can optionally filter the output by
recipe name (PN).

(This is a generalised version of the show-overlayed subcommand.)

(Bitbake rev: 05e86ba966f5a26721891c82b21afa48768a67cc)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake-layers: improve show-overlayed output</title>
<updated>2012-02-01T15:08:41+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-01-30T16:25:52+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=526264e7d74c8b5fad4ab5ec3303b2edfea98e61'/>
<id>urn:sha1:526264e7d74c8b5fad4ab5ec3303b2edfea98e61</id>
<content type='text'>
Make the following improvements to the show-overlayed subcommand:

* Show recipes that are overlayed when the version is higher or lower,
  not just when it is the same. This gives a much better picture of the
  influence each layer is having over the metadata used for building.
  This can be disabled with the -s option if you just want to see
  recipes with the same version as before.
* Default to showing name (PN), layer and version rather than the full
  path and filename. The old style formatting can be used by specifying
  the -f option.
* Mark skipped recipes as such in the output, and print them in the
  correct sorted place in the list rather than at the end
* Prefix/suffix title line with === so it can be filtered out easily in
  shell scripts if desired

(Bitbake rev: 43b473275d3cb2e60a14e4a52cdc4654b3f4e5e7)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>bitbake-layers: use directory name as layer name</title>
<updated>2012-02-01T15:08:41+00:00</updated>
<author>
<name>Paul Eggleton</name>
<email>paul.eggleton@linux.intel.com</email>
</author>
<published>2012-01-30T16:25:51+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=3d2f6d56109fc3ebe9c8e7fe0d84d6cd01a9e2fb'/>
<id>urn:sha1:3d2f6d56109fc3ebe9c8e7fe0d84d6cd01a9e2fb</id>
<content type='text'>
It turns out that using the collection name as specified within
layer.conf (i.e. what gets added to BBFILE_COLLECTIONS) as a name to
refer to the layer is not particularly useful, since layer creators
aren't necessarily setting these to a meaningful value - e.g. OE-Core
uses "normal", meta-oe uses "openembedded-layer", etc. In any case,
BitBake uses the directory name in its list of configured layers in the
system information presented upon starting a build, so let's just do the
same here and avoid confusion.

Also rename the get_append_layer function to get_file_layer since it is
in no way specific to bbappends.

(Bitbake rev: 35d2c1c618826e961dbf4b9889b829f469346d74)

Signed-off-by: Paul Eggleton &lt;paul.eggleton@linux.intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
