From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Khem Raj <raj.khem@gmail.com>
Cc: "poky@yoctoproject.org" <poky@yoctoproject.org>
Subject: Re: [PATCH] meta-yocto: Rename to meta-poky to better match its purpose
Date: Sun, 28 Feb 2016 23:11:44 +0000 [thread overview]
Message-ID: <1456701104.11498.173.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAMKF1srow_MbndaELxsBHQoJsBe23Tf2uXHFgD=9j1WsUk7R=w@mail.gmail.com>
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@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.
Cheers,
Richard
next prev parent reply other threads:[~2016-02-28 23:11 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-28 10:50 [PATCH] meta-yocto: Rename to meta-poky to better match its purpose Richard Purdie
2016-02-28 19:57 ` Khem Raj
2016-02-28 23:11 ` Richard Purdie [this message]
2016-02-29 1:50 ` Khem Raj
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1456701104.11498.173.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=poky@yoctoproject.org \
--cc=raj.khem@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.