Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Martin Jansa <martin.jansa@gmail.com>
To: Paul Eggleton <paul.eggleton@linux.intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: SRC_URI and latest HEAD revision with git
Date: Mon, 22 Jul 2013 14:42:04 +0200	[thread overview]
Message-ID: <20130722124204.GI9527@jama> (raw)
In-Reply-To: <3148065.skdr24gULv@helios>

[-- Attachment #1: Type: text/plain, Size: 2755 bytes --]

On Mon, Jul 22, 2013 at 12:08:06PM +0100, Paul Eggleton wrote:
> On Monday 22 July 2013 12:30:53 Steffen Sledz wrote:
> > On 22.07.2013 11:51, Paul Eggleton wrote:
> > > On Monday 22 July 2013 11:46:23 Steffen Sledz wrote:
> > >> On 22.07.2013 11:01, Nicolas Dechesne wrote:
> > >>> On Mon, Jul 22, 2013 at 8:21 AM, Steffen Sledz <sledz@dresearch-fe.de
> > >>> 
> > >>> <mailto:sledz@dresearch-fe.de>> wrote:
> > >>>> After being OE abstinent for some months i'd like to ask what is the
> > >>>> current suggested method for recipes building from the HEAD revision of
> > >>>> a git repository (we need this for continuous integration).
> > >>>> 
> > >>>> I read some RFC's in the ml about PKGV/PKGR stuff, but i miss a final
> > >>>> decision, documentation and a good example.>
> > >>> 
> > >>> you can use ${AUTOREV} for this purpose. You can look at poky-bleeding
> > >>> distro config for such an example.
> > >>> 
> > >>> e.g.
> > >>> http://git.yoctoproject.org/cgit/cgit.cgi/poky/tree/meta-yocto/conf/dist
> > >>> r
> > >>> o/include/poky-floating-revisions.inc
> > >> 
> > >> Hmmmm? This doesn't seem the work.
> > >> 
> > >> Here's what i tried in my recipe:
> > >> 
> > >> ------------> snip <------------
> > >> PR = "r3"
> > >> 
> > >> SRCREV="${AUTOREV}"
> > >> PV = "gitr${SRCPV}"
> > >> ------------> snip <------------
> > >> 
> > >> But i get package versions like
> > >> 
> > >>   gitr0+53b64e717404d282d0c58b7fa4a4e74ab2ca81ba-r3
> > >> 
> > >> where SRCPB is always 0. :(
> > >> 
> > >> A bit more description and/or a complete example would be very helpful.
> > > 
> > > If you want these to increment now AIUI you need to be using the PR
> > > server:
> > > 
> > > https://wiki.yoctoproject.org/wiki/PR_Service
> > 
> > This seems to be the thing we need.
> > 
> > But the description is not very helpful from the view of a recipe
> > maintainer. It describes mostly the server part.
> > 
> > * What do i have to write in my recipe?
> 
> Nothing special. If you used SRCPV in PV where you are using an SCM in 
> SRC_URI, that should be enough. The integer at the start of SRCREV will be 
> incremented automatically if the revision changes, and if it doesn't but other 
> values within the recipe change then PR will automatically be incremented 
> above the initial value set in the recipe.
> 
> > * What modifications in bitbake.conf, local.conf, ... are necessary?
> 
> I believe as described in the page I linked above you should only need to set 
> PRSERV_HOST.

If you need to support upgrade path from old LOCALCOUNT db in
PERSISTENT_DIR then you also need to migrate last numbers to PRSERV db.

-- 
Martin 'JaMa' Jansa     jabber: Martin.Jansa@gmail.com

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 205 bytes --]

  reply	other threads:[~2013-07-22 12:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-22  6:21 SRC_URI and latest HEAD revision with git Steffen Sledz
2013-07-22  9:01 ` Nicolas Dechesne
2013-07-22  9:46   ` Steffen Sledz
2013-07-22  9:51     ` Paul Eggleton
2013-07-22 10:30       ` Steffen Sledz
2013-07-22 11:08         ` Paul Eggleton
2013-07-22 12:42           ` Martin Jansa [this message]
2013-07-23  6:23           ` Steffen Sledz
2013-07-23  8:20             ` Paul Eggleton
2013-07-31 10:02       ` SRC_URI and latest HEAD revision with git (in oe-classic) Steffen Sledz
2013-07-31 12:50         ` [oe] " Paul Eggleton
2013-08-01  6:11           ` Steffen Sledz
2013-08-01 10:36             ` Martin Jansa
2013-08-01 10:52               ` Steffen Sledz
2013-08-01 11:37                 ` 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=20130722124204.GI9527@jama \
    --to=martin.jansa@gmail.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=paul.eggleton@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox