From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [RFC PATCH 0/2] introduce buildhistory.bbclass
Date: Mon, 05 Dec 2011 16:24:38 +0000 [thread overview]
Message-ID: <1323102278.25960.100.camel@ted> (raw)
In-Reply-To: <cover.1322782677.git.paul.eggleton@linux.intel.com>
On Thu, 2011-12-01 at 23:56 +0000, Paul Eggleton wrote:
> Here is the initial version of buildhistory.bbclass. It provides (most
> of) the functionality of testlab.bbclass and all functionality of
> packagehistory.bbclass.
>
> Changes/improvements over testlab:
> * Supports both rpm and ipk-based images
> * Works even if packaging data is removed in the final image
> * File listing is tidier and excludes date/time info so changes are more
> obvious
> * Produces a separate package list with just the package names (i.e. not
> the full file name).
> * Optional git commit occurs at the end of the build and is done outside
> of fakeroot
> * Can optionally push git commit to a remote repository
>
> Todo items:
> * There is no recording of licenses into the build history, in favour of
> Beth Flanagan's upcoming work on license.bbclass. I appreciate some may
> want this tracked in buildhistory - please comment. Could be something
> to add afterwards when Beth's work is integrated.
> * Deb-based packaging is not supported because I am unable to test it
> (see Yocto bug #1802).
>
> Note that an earlier version of this was merged accidentally to OE-core;
> this was subsequently reverted to allow proper review.
>
>
> Please review the following changes for suitability for inclusion. If you have
> any objections or suggestions for improvement, please respond to the patches. If
> you agree with the changes, please provide your Acked-by.
>
> The following changes since commit e57935dc18d576feb1003b48e7cdc72a444131b8:
>
> Revert "classes/buildhistory: add new output history collection class" (2011-12-01 23:00:52 +0000)
>
> are available in the git repository at:
> git://git.openembedded.org/openembedded-core-contrib paule/buildhistory
> http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/log/?h=paule/buildhistory
>
> Paul Eggleton (2):
> classes/buildhistory: add new output history collection class
> classes/buildhistory: merge in package history functionality
I've merged this. I don't think its perfect and I know Koen has found
one potential issue but it provides a base people can send patches
against :)
Cheers,
Richard
next prev parent reply other threads:[~2011-12-05 16:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-01 23:56 [RFC PATCH 0/2] introduce buildhistory.bbclass Paul Eggleton
2011-12-01 23:56 ` [RFC PATCH 1/2] classes/buildhistory: add new output history collection class Paul Eggleton
2011-12-02 10:03 ` Koen Kooi
2011-12-02 11:44 ` Paul Eggleton
2011-12-07 8:50 ` Koen Kooi
2011-12-07 11:38 ` Paul Eggleton
2012-01-08 23:04 ` Paul Eggleton
2011-12-01 23:56 ` [RFC PATCH 2/2] classes/buildhistory: merge in package history functionality Paul Eggleton
2011-12-02 10:15 ` Koen Kooi
2011-12-02 11:35 ` Paul Eggleton
2011-12-02 11:46 ` Koen Kooi
2011-12-02 11:49 ` Paul Eggleton
2011-12-02 20:46 ` Koen Kooi
2011-12-05 16:24 ` Richard Purdie [this message]
2011-12-05 16:51 ` [RFC PATCH 0/2] introduce buildhistory.bbclass Koen Kooi
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=1323102278.25960.100.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--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