From: Koen Kooi <koen@dominion.thruhere.net>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Correct versioning of unversioned source in git
Date: Thu, 13 Mar 2014 10:59:38 +0100 [thread overview]
Message-ID: <lfrvgd$3bd$1@ger.gmane.org> (raw)
In-Reply-To: <20140313100833.1910da0b@pcnovotny-t.fit.vutbr.cz>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Tomas Novotny schreef op 13-03-14 10:08:
> Hi all,
>
> there is a recipe sunxi-board-fex in meta-sunxi layer. That recipe
> fetches sources from unversioned git which contains definitions of some
> boards (in fact it is something like a store). I'm not sure with correct
> versioning in OE. Is that: PV = "1.0+git${SRCPV}" SRCREV =
> "<some_gitrev_I_want>" correct? Will be change of SRCREV (only) catched
> by build system (I'm curious how OE handles age of the rev in git)? Or do
> I need to raise PV to 1.1 and so on with every change to SRCREV?
The answer changes if you have more than one buildhost. If you have only one
buildhost and don't care about other people rebuilding the exact same
versions, 1.0+git${SRCPV} will work.
If you have more than one buildhost and/or care about other people
rebuilding the exact same, you'll need to increase PR (or PV) everytime
SRCREV changes. That will still cause some discrepancies if someone rebuilds
after >1 SRCREV change, but upgrade paths should work when increasing PV
(not with PR!).
regards,
Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)
Comment: GPGTools - http://gpgtools.org
iD8DBQFTIYGKMkyGM64RGpERAtHvAJ96mw6U8PacUt+DOagTFjWtwsNd2wCbB3nr
KSym/Y5aAMUbEKx61oNDiH0=
=Qvq7
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2014-03-13 9:59 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-13 9:08 Correct versioning of unversioned source in git Tomas Novotny
2014-03-13 9:59 ` Koen Kooi [this message]
2014-03-13 10:45 ` Paul Eggleton
2014-03-13 11:09 ` Koen Kooi
2014-03-13 11:14 ` Paul Eggleton
2014-03-13 11:17 ` Koen Kooi
2014-03-13 11:54 ` Paul Eggleton
2014-03-13 13:13 ` Koen Kooi
2014-03-14 11:53 ` Mike Looijmans
2014-03-13 21:15 ` Tomas Novotny
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='lfrvgd$3bd$1@ger.gmane.org' \
--to=koen@dominion.thruhere.net \
--cc=openembedded-devel@lists.openembedded.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.