From: Saul Wold <sgw@linux.intel.com>
To: Constantin Musca <constantinx.musca@intel.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH v3] log_srcrev.bbclass: add a bbclass for logging SRCREVs
Date: Tue, 26 Feb 2013 16:15:12 -0800 [thread overview]
Message-ID: <512D5010.9080107@linux.intel.com> (raw)
In-Reply-To: <1361891289-6777-1-git-send-email-constantinx.musca@intel.com>
On 02/26/2013 07:08 AM, Constantin Musca wrote:
> - add a task which creates a file for each package with the following
> format:
>
> ${BB_FILENAME},${SRC_URI},${SRCREV},${FROM_AUTOREV}
>
> [YOCTO #3041]
>
> Signed-off-by: Constantin Musca <constantinx.musca@intel.com>
> ---
> meta/classes/log_srcrev.bbclass | 15 +++++++++++++++
> 1 file changed, 15 insertions(+)
> create mode 100644 meta/classes/log_srcrev.bbclass
>
> diff --git a/meta/classes/log_srcrev.bbclass b/meta/classes/log_srcrev.bbclass
> new file mode 100644
> index 0000000..a04702c
> --- /dev/null
> +++ b/meta/classes/log_srcrev.bbclass
> @@ -0,0 +1,15 @@
> +python do_log_srcrev () {
> + srcrev = d.getVar('SRCREV', True)
> + if srcrev:
> + bbfile = d.getVar('BB_FILENAME', True)
> + src_uri = d.getVar('SRC_URI', True)
> + from_autorev = 'yes' if d.getVar('SRCREV', False) == 'AUTOINC' else 'no'
> +
> + srcrevfile = d.expand('${TMPDIR}/srcrevs/${MULTIMACH_TARGET_SYS}/${BP}')
> + bb.utils.mkdirhier(os.path.dirname(srcrevfile))
> +
> + with open(srcrevfile, 'w') as f:
> + f.write(','.join([bbfile, src_uri, srcrev, from_autorev]))
> +}
> +
> +addtask do_log_srcrev after do_fetch
>
Otavio makes a good point, this might be something to consider putting
it in to the RecipeInfo in buildhistory.bbclass and extend the
write_pkghistory(), but maybe write the file with a different name
latest_srcrev
Sau!
prev parent reply other threads:[~2013-02-27 0:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-26 15:08 [PATCH v3] log_srcrev.bbclass: add a bbclass for logging SRCREVs Constantin Musca
2013-02-27 0:15 ` Saul Wold [this message]
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=512D5010.9080107@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=constantinx.musca@intel.com \
--cc=openembedded-core@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