From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: richard.purdie@linuxfoundation.org
Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org,
saul.wold@intel.com
Subject: [PATCH 0/1] linux-yocto: recipe renames
Date: Fri, 10 Jun 2011 14:42:22 -0400 [thread overview]
Message-ID: <cover.1307730764.git.bruce.ashfield@windriver.com> (raw)
Richard/Saul,
Here's the completion of a long standing 'nit of ours
where the kernel version isn't all that obvious from
the name of the linux-yocto recipes. As we finally
cycle a kernel version out the bottom (2.6.34) the
issue came to a head (did you mean the old -stable
or the new -stable? .. etc).
So here are the recipe renames to fix things. I'll
quote the patch here:
[
linux-yocto: rename recipes to explicitly indicate version
The existing recipe names for the linux-yocto kernel builds
worked well when there was a single, or two versions of the
kernel available. But with the impending kernel updates and
retirement of older kernels, the re-use of the same recipes
for different kernel versions violates the principle of least
surprise.
To address this, the recipes are being renamed as follows:
linux-yocto_git.bb -> linux-yocto_2.6.37.bb
linux-yocto-stable_git.bb -> linux-yocto_2.6.34.bb
There continue to be versionless recipe names that feed into
versioned recipes at the appropriate points. They are:
linux-yocto-dev.bb (tracking the latest yocto dev kernel)
linux-yocto-korg_head.bb (tracking korg kernels)
There are no existing users of linux-yocto-stable in the master
branches to convert to the new naming, so these changes work
in isolation.
Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
]
I'm sending follow up patches to any other users that I know
of, but I can't say that I know of any and everyone with a
bbappends that will no longer match.
So I'll leave it up to you for how you want to go about the
transition, but let me know, so I can get the known users
synchronized when this goes into master.
If you'd rather not jave the renames, I can simply add the new recipes
and we can remove the old ones at some more distant point in
the future when we know it to be safe. The more I think about it,
this may be the best option to keep things from breaking, but I'll
wait to hear before resending with that as the change.
Cheers,
Bruce
The following changes since commit b30cb584a738915113e88b7db1028d53b2bae5f9:
Richard Purdie (1):
Revert "gcc: rebase the patch to avoid patch rejection"
are available in the git repository at:
git://git.pokylinux.org/poky-contrib zedd/kernel
http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=zedd/kernel
Bruce Ashfield (1):
linux-yocto: rename recipes to explicitly indicate version
...x-yocto-stable_git.bb => linux-yocto_2.6.34.bb} | 0
.../{linux-yocto_git.bb => linux-yocto_2.6.37.bb} | 0
2 files changed, 0 insertions(+), 0 deletions(-)
rename meta/recipes-kernel/linux/{linux-yocto-stable_git.bb => linux-yocto_2.6.34.bb} (100%)
rename meta/recipes-kernel/linux/{linux-yocto_git.bb => linux-yocto_2.6.37.bb} (100%)
next reply other threads:[~2011-06-10 18:47 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-06-10 18:42 Bruce Ashfield [this message]
2011-06-10 18:42 ` [PATCH 1/1] linux-yocto: rename recipes to explicitly indicate version Bruce Ashfield
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=cover.1307730764.git.bruce.ashfield@windriver.com \
--to=bruce.ashfield@windriver.com \
--cc=dvhart@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=richard.purdie@linuxfoundation.org \
--cc=saul.wold@intel.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox