<feed xmlns='http://www.w3.org/2005/Atom'>
<title>linux/poky.git/meta-poky/classes, branch yocto-5.0.9</title>
<subtitle>Mirror of git.yoctoproject.org/poky</subtitle>
<id>https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-5.0.9</id>
<link rel='self' href='https://git.enea.com/cgit/linux/poky.git/atom?h=yocto-5.0.9'/>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/'/>
<updated>2024-04-14T05:29:00+00:00</updated>
<entry>
<title>poky-bleeding.bbclass: Remove use of SRCPV</title>
<updated>2024-04-14T05:29:00+00:00</updated>
<author>
<name>Khem Raj</name>
<email>raj.khem@gmail.com</email>
</author>
<published>2024-02-29T06:21:53+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9a197e4f92b97d216dee902f16b448f55d50876b'/>
<id>urn:sha1:9a197e4f92b97d216dee902f16b448f55d50876b</id>
<content type='text'>
(From meta-yocto rev: a287fabcc55cbe46bc660ad45e03f94428824386)

(From meta-yocto rev: 705258d7ad70b4b69f4c5b5397101853ae7ba4d3)

Signed-off-by: Khem Raj &lt;raj.khem@gmail.com&gt;
Signed-off-by: Alexandre Belloni &lt;alexandre.belloni@bootlin.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>poky-bleeding: Update and rework</title>
<updated>2023-03-21T22:47:01+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2023-03-15T17:59:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=c7ee2d0236184045d46cfffa9f8822d3118baaf6'/>
<id>urn:sha1:c7ee2d0236184045d46cfffa9f8822d3118baaf6</id>
<content type='text'>
This distro setting has bitrotted quite badly but the idea remains
a good one. Try and improve things by:

* using a class and a list of recipes to make things more readable
* drop settings for recipes which no longer use git
* drop obsolete PREFERRED_VERSION settings
* add a provider switch to use linux-yocto-dev
* reword to avoid "package" confusion with recipe

The distro then builds and highlighted a number of matchbox
issues which other patches address and improve.

(From meta-yocto rev: 00e974484d771dd015af1f2c0c547135555d24d0)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>poky-sanity.bbclass: update conf/templateconf.cfg for existing installations</title>
<updated>2016-03-26T07:34:59+00:00</updated>
<author>
<name>Bill Randle</name>
<email>william.c.randle@intel.com</email>
</author>
<published>2016-03-21T18:24:48+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=54eca753082af7d4c44379f879945f449d4f56cf'/>
<id>urn:sha1:54eca753082af7d4c44379f879945f449d4f56cf</id>
<content type='text'>
Updates of existing installations for the meta-yocto to meta-poky transition will
update the bblayers.conf file, but not the templateconf.cfg file. This
patch updates the template file to point to meta-poky/conf, if necessary.

Fixes [YOCTO #9278]

(From meta-yocto rev: e560e9b157fd53cccbe73659b44777715660f0b2)

Signed-off-by: Bill Randle &lt;william.c.randle@intel.com&gt;
Signed-off-by: Ross Burton &lt;ross.burton@intel.com&gt;
Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
<entry>
<title>meta-yocto: Rename to meta-poky to better match its purpose</title>
<updated>2016-02-28T11:31:17+00:00</updated>
<author>
<name>Richard Purdie</name>
<email>richard.purdie@linuxfoundation.org</email>
</author>
<published>2016-02-16T16:42:58+00:00</published>
<link rel='alternate' type='text/html' href='https://git.enea.com/cgit/linux/poky.git/commit/?id=9d5483c37523ff3d334c98cafb848282b54962cd'/>
<id>urn:sha1:9d5483c37523ff3d334c98cafb848282b54962cd</id>
<content type='text'>
"poky" is the reference distribution for the Yocto Project. This renames
the layer within the meta-yocto repository to meta-poky, better matching
what that layer contains.

A layer.conf file is left behind as this is the only way which allows
existing builds to migrate safely to the new name. It will be removed
at some future point.

This change requires the corresponding OE-Core change to handle the
migration and the changes to the infrastructure to support this.

(From meta-yocto rev: d0c88df2e14672fca4ebbde93c5efbcd0e4fa9b6)

Signed-off-by: Richard Purdie &lt;richard.purdie@linuxfoundation.org&gt;
</content>
</entry>
</feed>
