Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Steffen Sledz <sledz@dresearch-fe.de>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: SRC_URI and latest HEAD revision with git
Date: Tue, 23 Jul 2013 09:20:16 +0100	[thread overview]
Message-ID: <6740877.OeitjjUtks@helios> (raw)
In-Reply-To: <51EE217A.4040709@dresearch-fe.de>

On Tuesday 23 July 2013 08:23:54 Steffen Sledz wrote:
> On 22.07.2013 13:08, Paul Eggleton wrote:
> > On Monday 22 July 2013 12:30:53 Steffen Sledz wrote:
> >> On 22.07.2013 11:51, Paul Eggleton wrote:
> >>> 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.
> 
> You're right. This works. ;-)
> 
> I've two points more:
> * The Wiki-Page mentions the bitbake-prserv-tool. Where can this be found?

Perhaps confusingly it's part of OE-Core. I haven't looked at it to see if 
there's anything OE-specific about it that meant it had to be there rather than 
supplied with bitbake.

> * Does anyone have systemd configs or sysvinit scripts for handling the
> bitbake-prserv?

I don't, but perhaps others do.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre


  reply	other threads:[~2013-07-23  8:20 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
2013-07-23  6:23           ` Steffen Sledz
2013-07-23  8:20             ` Paul Eggleton [this message]
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=6740877.OeitjjUtks@helios \
    --to=paul.eggleton@linux.intel.com \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=sledz@dresearch-fe.de \
    /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