From: Denys Dmytriyenko <denis@denix.org>
To: openembedded-devel@lists.openembedded.org
Subject: Use AUTOREV and have revision/commit number in package name?
Date: Wed, 19 Aug 2009 23:28:02 -0400 [thread overview]
Message-ID: <20090820032802.GA32010@denix.org> (raw)
All,
I've been playing with AUTOREV for some time now and also asked this question
before on the IRC, but so far there seems to be no easy solution to the
problem in subject.
Usually, when a package is built from an SCM repository, SRCREV is set to a
specific commit#/tag etc. And SRCREV is also usually referenced from PV (like
PV = "X.Y.Z-scmr${SRCREV}") to have the revision/commit number in the package
name, to easily track different builds.
Now, when SRCREV = "${AUTOREV}", AUTOREV gets resolved into a Python function,
which does the magic of fetching the latest snapshot from a repository. But
now if PV contains references to SRCREV, it breaks (undesrandably), since
SRCREV gets resolved in do_fetch and PV needs to be resolved early on.
Are there any standard ways to work around this limitation?
I was thinking this maybe quite tricky, since the actual revision number used,
is not known until do_fetch runs the actual checkout, at which time changing
PV is too late, as temp/work is already created and so on. So, would it be
possible to hack one of the do_package tasks to add the actual revision/commit
number to a final package name, bypassing changing PV/PR?
Any thoughts? Feel free to throw ideas. Thanks.
--
Denys
next reply other threads:[~2009-08-20 3:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-20 3:28 Denys Dmytriyenko [this message]
2009-08-20 5:52 ` Use AUTOREV and have revision/commit number in package name? Holger Hans Peter Freyther
2009-08-20 7:10 ` Denys Dmytriyenko
2009-08-20 8:34 ` Koen Kooi
2009-08-20 9:01 ` Denys Dmytriyenko
2009-08-20 9:46 ` Martin Jansa
2009-08-20 10:26 ` Denys Dmytriyenko
2009-08-26 19:55 ` Martin Jansa
2009-08-20 9:48 ` Graeme Gregory
2009-08-20 9:13 ` Graeme Gregory
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=20090820032802.GA32010@denix.org \
--to=denis@denix.org \
--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.