From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from dan.rpsys.net (dan.rpsys.net [93.97.175.187]) by mail.openembedded.org (Postfix) with ESMTP id E376E610CD for ; Fri, 28 Mar 2014 13:32:34 +0000 (UTC) Received: from localhost (dan.rpsys.net [127.0.0.1]) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu4) with ESMTP id s2SDWFF9019238; Fri, 28 Mar 2014 13:32:15 GMT X-Virus-Scanned: Debian amavisd-new at dan.rpsys.net Received: from dan.rpsys.net ([127.0.0.1]) by localhost (dan.rpsys.net [127.0.0.1]) (amavisd-new, port 10024) with LMTP id VYaOqZj3e1mo; Fri, 28 Mar 2014 13:32:14 +0000 (GMT) Received: from [192.168.3.10] (rpvlan0 [192.168.3.10]) (authenticated bits=0) by dan.rpsys.net (8.14.4/8.14.4/Debian-2.1ubuntu1) with ESMTP id s2SDW747019232 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES128-SHA bits=128 verify=NOT); Fri, 28 Mar 2014 13:32:09 GMT Message-ID: <1396013522.14790.4.camel@ted> From: Richard Purdie To: Bruce Ashfield Date: Fri, 28 Mar 2014 13:32:02 +0000 In-Reply-To: <5335707F.7050105@windriver.com> References: <1395999939.24890.170.camel@ted> <5335707F.7050105@windriver.com> X-Mailer: Evolution 3.8.4-0ubuntu1 Mime-Version: 1.0 Cc: dvhart@linux.intel.com, openembedded-core@lists.openembedded.org Subject: Re: [PATCH 10/13] linux-yocto/3.14: introduce versioned recipes X-BeenThere: openembedded-core@lists.openembedded.org X-Mailman-Version: 2.1.12 Precedence: list List-Id: Patches and discussions about the oe-core layer List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 28 Mar 2014 13:32:35 -0000 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit On Fri, 2014-03-28 at 08:52 -0400, Bruce Ashfield wrote: > 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 > >> --- > >> 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 ? A PE bump would work however we try not to use those, they're a last resort to correct things we can't otherwise fix. The PR server doesn't help here although in future I do hope we can teach it about PE too. > 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 ? Might as well wait over the weekend. If Linus does go for a rc9, we'll need to merge a version with the modified PV though. In the meantime I might pull this series into master-next for testing but it will not get added to master in its current form. Cheers, Richard