From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Brad Litterell <brad@evidence.com>
Cc: yocto@yoctoproject.org
Subject: Re: Setting PV dynamically in a recipe
Date: Tue, 17 Dec 2013 20:24:38 +0000 [thread overview]
Message-ID: <14453943.1Qpn4azGq8@helios> (raw)
In-Reply-To: <E51394554A503C4E852F9BEE46B03E8D019AC7CA@TI-THOR.tasernet.com>
Hi Brad,
On Tuesday 17 December 2013 19:46:11 Brad Litterell wrote:
> Thank you for the reply. However, That's not what I'm looking for. I
> already get the latest version of the source code.
>
> What I'm really after is the ability to generate output packages that have
> increasing version numbers so I can use the package manager to update them.
>
> I think Martin's subsequent reply is the secret to use PKGV. I didn't know
> about that variable.
You don't need to use any special classes to get this behaviour. Put this in
your recipe (replacing 1.2.3 with the appropriate base version you are
building):
PV = "1.2.3+git${SRCPV}"
and enable the PR service, which will ensure SRCREV changes always increment
the version properly:
http://www.yoctoproject.org/docs/current/dev-manual/dev-manual.html#working-with-a-pr-service
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2013-12-17 20:24 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-12-17 8:16 Setting PV dynamically in a recipe Brad Litterell
2013-12-17 9:41 ` zhenhua.luo
2013-12-17 19:46 ` Brad Litterell
2013-12-17 20:24 ` Paul Eggleton [this message]
2013-12-18 1:29 ` Brad Litterell
2013-12-18 9:36 ` Martin Jansa
2013-12-20 3:09 ` Brad Litterell
2013-12-20 9:34 ` Martin Jansa
2013-12-20 9:39 ` Brad Litterell
2013-12-20 10:01 ` Martin Jansa
2013-12-20 10:03 ` Brad Litterell
2013-12-20 10:11 ` Brad Litterell
2013-12-20 11:26 ` Martin Jansa
2013-12-17 14:01 ` Martin Jansa
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=14453943.1Qpn4azGq8@helios \
--to=paul.eggleton@linux.intel.com \
--cc=brad@evidence.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.