All of lore.kernel.org
 help / color / mirror / Atom feed
From: Darren Hart <dvhart@linux.intel.com>
To: "poky@yoctoproject.org" <poky@yoctoproject.org>
Cc: Marcin Juszkiewicz <marcin.juszkiewicz@linaro.org>
Subject: Proper recipe naming and PV definition
Date: Mon, 06 Dec 2010 15:17:14 -0800	[thread overview]
Message-ID: <4CFD6EFA.8050503@linux.intel.com> (raw)

I'm having trouble determining what the best practice is for naming a 
linux kernel recipe.

The meta-linaro layer contains a linux-linaro recipe, and eventually I'd 
like it to contain two. One for the stable kernel and one for the 
development kernel. These are currently 2.6.35 and 2.6.37 respectively. 
I currently have:

linux-linaro-2.6.35_git.bb
PV=2.6.35

This results in directory names in the build tree like:
linux-linaro-2.6.36_2.6.35 (or similar, with the version duplicated). As 
I understand it, the PV _must_ contain a standard Linux kernel version 
along the lines of 2.6.[0-9]+-* (and parsing fails without it).

In order to both track the version and distinguish between stable and 
dev, would something like the following be appropriate? This also 
replaces _git with _KERNELVER (as proposed by Marcin).

linux-linaro-stable_2.6.35.bb
PV=2.6.35+git${SRCREV}

linux-linaro-dev_2.6.37.bb
PV=2.6.37+git${SRCREV}

Thanks,

-- 
Darren Hart
Yocto Linux Kernel


             reply	other threads:[~2010-12-06 23:17 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-06 23:17 Darren Hart [this message]
2010-12-06 23:24 ` Proper recipe naming and PV definition Koen Kooi
2010-12-06 23:59   ` Darren Hart
2010-12-07  0:53 ` Bruce Ashfield
2010-12-07  3:46   ` Darren Hart
2010-12-07  4:02     ` Chris Larson
2010-12-07 15:23       ` Bruce Ashfield
2010-12-07 15:20     ` 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=4CFD6EFA.8050503@linux.intel.com \
    --to=dvhart@linux.intel.com \
    --cc=marcin.juszkiewicz@linaro.org \
    --cc=poky@yoctoproject.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 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.