All of lore.kernel.org
 help / color / mirror / Atom feed
From: Trevor Woerner <twoerner@gmail.com>
To: yocto@yoctoproject.org
Subject: auto kernel version
Date: Sat, 18 Mar 2017 04:07:05 -0400	[thread overview]
Message-ID: <20170318080705.GA11330@linux-uys3> (raw)

Hi,

Let's say I wanted to create a recipe to follow Linus' mainline or a recipe
to follow GregKH's staging-next. In those cases I wouldn't want to nail them
down with a version, I'd want to do AUTOREV. So I wouldn't put a version in
the recipe filename (linus-mainline.bb or gregkh-staging-next_git.bb).
But I can't seem to get away with not having some sort of version string
(LINUX_VERSION, PV) in the recipe itself. Is it not possible to extract a PV
or LINUX_VERSION automatically? Otherwise I'll need to update the recipe and
commit with every release (which isn't the end of the world, but adds to the
maintenance).

	SUMMARY = "GregKH's Staging-Next"
	SECTION = "kernel"
	LICENSE = "GPLv2"

	inherit kernel
	require recipes-kernel/linux/linux-dtb.inc

	LIC_FILES_CHKSUM = "file://COPYING;md5=d7810fab7487fb0aad327b76f1be7cd7"

	SRC_URI = "git://git.kernel.org/pub/scm/linux/kernel/git/gregkh/staging.git;branch=staging-next"
	SRC_URI_append_rk3288 = " file://defconfig"
	SRC_URI_append_intel-corei7-64 = " file://defconfig"
	SRCREV = "${AUTOREV}"

	LINUX_VERSION = "4.11"
	PV = "${LINUX_VERSION}+git${SRCPV}"
	S = "${WORKDIR}/git"

	DEPENDS += "xz-native bc-native coreutils-native"


             reply	other threads:[~2017-03-18  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-18  8:07 Trevor Woerner [this message]
2017-03-18  9:42 ` auto kernel version Paul Barker

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=20170318080705.GA11330@linux-uys3 \
    --to=twoerner@gmail.com \
    --cc=yocto@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.