From: Martin Jansa <martin.jansa@gmail.com>
To: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Cc: yocto@yoctoproject.org
Subject: Re: : git tag and PV variable
Date: Wed, 24 Feb 2016 17:39:15 +0100 [thread overview]
Message-ID: <20160224163915.GG2560@jama> (raw)
In-Reply-To: <56CDD400.8090805@linux.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1349 bytes --]
On Wed, Feb 24, 2016 at 06:02:08PM +0200, Alexander Kanavin wrote:
> On 02/24/2016 05:35 PM, Khem Raj wrote:
> >
> > I have this command in my qmake pro files:____
> >
> > VERSION = $$system(git describe --abbrev=0 --tags)____
> >
> > __ __
> >
> > I would like to have the package manager follow the tag versioning.____
> >
> > __ __
> >
> > Which means I would like to have something like:____
> >
> > PV = "git describe --abbrev=0 --tags"____
> >
> > SRC_URI = "${STUDIEL_GIT}/core.git;protocol=file;tag=${PV}"____
> >
> > __ __
> >
> > It does not work for sure. What is the correct way to do this ?
> >
> >
> > SRC_URI is required by fetcher and there is nothing to git describe
> > before it is fetched.
> > so thats your problem.
>
> It's possible however to write an external script that updates the PV
> version in the recipe, but it needs to be run outside of bitbake.
We already have 2 bbclasses to do that
meta-openembedded/meta-oe/classes/gitpkgv.bbclass
meta-openembedded/meta-oe/classes/gitver.bbclass
there were some plans to get one of them to oe-core, but IIRC it was
decided to create support for this in bitbake fetcher, I'm not sure how
far it went with actual implementation.
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2016-02-24 16:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-24 15:29 : git tag and PV variable GUEYTAT Julien
2016-02-24 15:35 ` Khem Raj
2016-02-24 16:02 ` Alexander Kanavin
2016-02-24 16:39 ` Martin Jansa [this message]
2016-02-24 18:09 ` Maciej Borzecki
2016-02-25 13:19 ` GUEYTAT Julien
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=20160224163915.GG2560@jama \
--to=martin.jansa@gmail.com \
--cc=alexander.kanavin@linux.intel.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.