[poky] [PATCH] meta-yocto: Rename to meta-poky to better match its purpose

[Khem Raj]

> On Feb 28, 2016, at 3:11 PM, Richard Purdie <richard.purdie at linuxfoundation.org> wrote:
> 
> On Sun, 2016-02-28 at 11:57 -0800, Khem Raj wrote:
>> On Sun, Feb 28, 2016 at 2:50 AM, Richard Purdie
>> <richard.purdie at linuxfoundation.org> wrote:
>>> "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.
>>> 
>> 
>> This is a welcome change. Do we rename meta-yocto-bsp to something as
>> well ?
> 
> I thought about that. These truly are the Yocto Project reference/test
> BSPs, they're not really poky so I think the name is right as it is.
> 
>> may people confuse which layers to use with poky for some machines
>> which exist in both places e.g. beaglebone may be renaming the
>> machine name could solve this issue as well.
> 
> That is the first time that has been proposed. I'm not entirely sure it
> would help, it might be something improving the documentation might
> help more.

I have seen people ask should they use meta-ti or Yocto provided BSP for beaglebone
which is official supported BSP, documentation can help surely. however, avoiding
namespace conflicts could be better. Having said that it does not preclude
the wider problem which might happen involving other BSP layers providing same
machine configurations.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 204 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.yoctoproject.org/pipermail/poky/attachments/20160228/f42c75e8/attachment.pgp>