From: pieterg <pieterg@gmx.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: AUTOREV and SRCPV
Date: Fri, 4 Jun 2010 10:44:41 +0200 [thread overview]
Message-ID: <201006041044.42032.pieterg@gmx.com> (raw)
In-Reply-To: <1275640257.4657.84.camel@lenovo.internal.reciva.com>
On Friday 04 June 2010 10:30:57 Phil Blundell wrote:
> On Fri, 2010-06-04 at 10:24 +0200, pieterg wrote:
> > I probably don't know enough about the bitbake internals to see how to
> > fix my problem with that, could you please point me in the right
> > direction? I think in case of AUTOREV I would still need some way to
> > automatically include a sortable revision count in PKGV, so the actual
> > problem would only move from PV to PKGV.
>
> That's correct: essentially it is just moving the SRCPV-equivalent thing
> from PV to PKGV. But, PKGV only needs to be evaluated during the
> do_package step, not at parse time, so you only incur the cost and risk
> of running git rev-list (or whatever) for packages that you are actually
> building rather than for all recipes in your source tree.
I'm starting to see your point. That would really allow a much nicer AUTOREV
implementation.
But in that case I'm not getting away with a simple workaround I'm afraid...
Rgds, Pieter
next prev parent reply other threads:[~2010-06-04 8:49 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-02 21:51 AUTOREV and SRCPV pieterg
2010-06-03 4:35 ` Martin Jansa
2010-06-03 7:15 ` pieterg
2010-06-03 7:37 ` Martin Jansa
2010-06-03 8:02 ` pieterg
2010-06-03 8:27 ` Martin Jansa
2010-06-03 8:44 ` pieterg
2010-06-03 9:22 ` pieterg
2010-06-03 8:13 ` Phil Blundell
2010-06-03 8:30 ` Martin Jansa
2010-06-03 8:37 ` Phil Blundell
2010-06-03 8:46 ` Martin Jansa
2010-06-03 8:55 ` Phil Blundell
2010-06-03 16:35 ` Phil Blundell
2010-06-04 8:24 ` pieterg
2010-06-04 8:30 ` Phil Blundell
2010-06-04 8:44 ` pieterg [this message]
2010-06-04 11:03 ` Phil Blundell
2010-06-05 10:36 ` pieterg
2010-06-06 21:00 ` Phil Blundell
2010-06-07 0:13 ` Khem Raj
2010-06-08 10:09 ` Phil Blundell
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=201006041044.42032.pieterg@gmx.com \
--to=pieterg@gmx.com \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox