From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>,
Christopher Larson <kergoth@gmail.com>,
Mark Hatle <mark.hatle@windriver.com>
Subject: Re: [PATCH 0/3] Realize archiver.bbclass
Date: Mon, 05 Mar 2012 14:28:20 -0800 [thread overview]
Message-ID: <4F553E04.3040306@linux.intel.com> (raw)
In-Reply-To: <cover.1330771239.git.xiaofeng.yan@windriver.com>
On 03/03/2012 02:53 AM, Xiaofeng Yan wrote:
> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>
> archiver.bbclass is for archiving sources , patches and logs including .bb and .inc files by configuring archiver_configure.bbclass which control what a archiving package should include.
> For archiving a source rpm package, I add some functions to package_rpm.bbclass.
> I also merge source_pkg.bbclass to archiver.bbclass due to their similar functions.
>
Are you going to deprecate/remove the other classes sourcepkg.bbclass,
src_distribute.bbclass, src_distribute_local.bbclass and
copyleft_compliance.bbclass
I am still reviewing this and would like to get ACKs from Chris and Mark.
This is going to require some review and testing. I also sent and email
about the archiver_configure class.
Can you please let us know how you tested, this is an important change
and we would like to get it close to correct the first time through.
Thanks for your effort on this.
Sau!
> Pull URL: git://git.pokylinux.org/poky-contrib.git
> Branch: xiaofeng/1977
> Browse: http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=xiaofeng/1977
>
> Thanks,
> Xiaofeng Yan<xiaofeng.yan@windriver.com>
> ---
>
>
> Xiaofeng Yan (3):
> package_rpm.bbclass: Add srpm function
> archiver.bbclass: archive sources, patches,logs to tarball
> archiver_configure.bbclass: configure the content for archiving
> package
>
> meta/classes/archiver.bbclass | 393 +++++++++++++++++++++++++++++++
> meta/classes/archiver_configure.bbclass | 35 +++
> meta/classes/package_rpm.bbclass | 54 ++++-
> 3 files changed, 479 insertions(+), 3 deletions(-)
> create mode 100644 meta/classes/archiver.bbclass
> create mode 100644 meta/classes/archiver_configure.bbclass
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
next prev parent reply other threads:[~2012-03-05 22:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-03 10:53 [PATCH 0/3] Realize archiver.bbclass Xiaofeng Yan
2012-03-03 10:54 ` [PATCH 1/3] package_rpm.bbclass: Add srpm function Xiaofeng Yan
2012-03-05 17:04 ` Colin Walters
2012-03-03 10:54 ` [PATCH 2/3] archiver.bbclass: archive sources, patches, logs to tarball Xiaofeng Yan
2012-03-12 18:54 ` Mark Hatle
2012-03-13 7:29 ` Xiaofeng Yan
2012-03-03 10:54 ` [PATCH 3/3] archiver_configure.bbclass: configure the content for archiving package Xiaofeng Yan
2012-03-05 22:18 ` Saul Wold
2012-03-06 11:11 ` Xiaofeng Yan
2012-03-12 18:58 ` Mark Hatle
2012-03-13 6:48 ` Xiaofeng Yan
2012-03-05 22:28 ` Saul Wold [this message]
2012-03-06 11:16 ` [PATCH 0/3] Realize archiver.bbclass Xiaofeng Yan
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=4F553E04.3040306@linux.intel.com \
--to=sgw@linux.intel.com \
--cc=kergoth@gmail.com \
--cc=mark.hatle@windriver.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