Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Bruce Ashfield <bruce.ashfield@windriver.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes
Date: Fri, 28 Mar 2014 08:52:15 -0400	[thread overview]
Message-ID: <5335707F.7050105@windriver.com> (raw)
In-Reply-To: <1395999939.24890.170.camel@ted>

On 14-03-28 05:45 AM, Richard Purdie wrote:
> On Thu, 2014-03-27 at 14:25 -0400, Bruce Ashfield wrote:
>> The release kernel for Yocto 1.5 is the 3.14 kernel, so we introduce
>> the versioned recipes here.
>>
>> Signed-off-by: Bruce Ashfield <bruce.ashfield@windriver.com>
>> ---
>>   meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb | 21 ++++++++++++
>>   meta/recipes-kernel/linux/linux-yocto_3.14.bb      | 37 ++++++++++++++++++++++
>>   2 files changed, 58 insertions(+)
>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>>   create mode 100644 meta/recipes-kernel/linux/linux-yocto_3.14.bb
>>
>> diff --git a/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>> new file mode 100644
>> index 000000000000..8faa9584acf0
>> --- /dev/null
>> +++ b/meta/recipes-kernel/linux/linux-yocto-tiny_3.14.bb
>> @@ -0,0 +1,21 @@
>> +require recipes-kernel/linux/linux-yocto.inc
>> +
>> +KBRANCH = "standard/tiny/base"
>> +LINUX_KERNEL_TYPE = "tiny"
>> +KCONFIG_MODE = "--allnoconfig"
>> +
>> +LINUX_VERSION ?= "3.14-rc8"
>> +
>> +KMETA = "meta"
>> +
>> +SRCREV_machine ?= "fecc3fd7d31bd93766ff4f0431fecdbbfa4c3a7c"
>> +SRCREV_meta ?= "3689f99f4d2a051e8d3ff72345a67d4d04a88020"
>> +
>> +PV = "${LINUX_VERSION}+git${SRCPV}"
>
> I'm afraid we can't do this in such a simple way. The big issue is that
> according to our version comparison functions (in bitbake and in the
> package managers), "3.14-rc8" > "3.14". This will then break updates
> from package feeds.
>
> The traditional way we've worked around this in times gone by is the
> rather ugly:
>
> PV = "3.13+3.14-rc8+git${SRCPV}"
>
> since in this case "3.14" > "3.13+3.14-rc8"
>
> The better way to handle this would be "3.14~rc8" however not all of our
> package backends have support for "~" at this point so we can't do that.
> There is a long standing bug open about this.
>
> The same issue also applies to the libc-headers recipe.

eeee. Since I don't do package feeds, it's never been a problem for me.

Wouldn't PE bump when I go to 3.14 work as well ? Or does that go away
with the PR sever as well ?

I can muck with PV, or we can hold until Linus releases over the
weekend, and I go with the released PVs.

What's your preference ?

Bruce

>
> Cheers,
>
> Richard
>
>



  reply	other threads:[~2014-03-28 12:52 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-27 18:24 [PATCH 00/13] linux-yocto: 3.4, 3.8, 3.10 AND 3.14 updates Bruce Ashfield
2014-03-27 18:24 ` [PATCH 01/13] linux-yocto/3.10: intel-core*/common configuration updates Bruce Ashfield
2014-03-27 18:24 ` [PATCH 02/13] linux-yocto/3.4: update mohonpeak.cfg for SATA, SMBus, LPC, WDT, crypto & highmem64g Bruce Ashfield
2014-03-27 18:24 ` [PATCH 03/13] linux-yocto/3.10: update EFI configuration Bruce Ashfield
2014-03-27 18:24 ` [PATCH 04/13] linux-yocto/3.10: update to v3.10.33 Bruce Ashfield
2014-03-27 18:25 ` [PATCH 05/13] linux-yocto/3.10: add valleyisland io Bruce Ashfield
2014-03-27 18:25 ` [PATCH 06/13] linux-yocto/3.10: update to v3.10.34 Bruce Ashfield
2014-03-27 18:25 ` [PATCH 07/13] linux-yocto/3.10: update intel common meta data Bruce Ashfield
2014-03-27 18:25 ` [PATCH 08/13] linux-yocto/3.10: fix drm build failure Bruce Ashfield
2014-03-27 18:25 ` [PATCH 09/13] linux-yocto/3.8: remove versioned recipes Bruce Ashfield
2014-03-27 18:25 ` [PATCH 10/13] linux-yocto/3.14: introduce " Bruce Ashfield
2014-03-28  9:45   ` Richard Purdie
2014-03-28 12:52     ` Bruce Ashfield [this message]
2014-03-28 13:05       ` Martin Jansa
2014-03-28 13:32       ` Richard Purdie
2014-03-28 13:56         ` Bruce Ashfield
2014-03-28 17:33         ` Bruce Ashfield
2014-03-27 18:25 ` [PATCH 11/13] linux-libc-headers: add 3.14 libc headers Bruce Ashfield
2014-03-27 18:25 ` [PATCH 12/13] libc-headers: set TC default to 3.14 Bruce Ashfield
2014-03-27 18:25 ` [PATCH 13/13] linux-libc-headers: remove 3.10 recipe 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=5335707F.7050105@windriver.com \
    --to=bruce.ashfield@windriver.com \
    --cc=dvhart@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=richard.purdie@linuxfoundation.org \
    /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