From: wenzong fan <wenzong.fan@windriver.com>
To: Saul Wold <sgw@linux.intel.com>
Cc: "Yan, Xiaofeng" <Xiaofeng.Yan@windriver.com>,
Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH v2 0/1] archive.bbclass: archive work directory
Date: Thu, 12 Jan 2012 16:25:09 +0800 [thread overview]
Message-ID: <4F0E98E5.3020302@windriver.com> (raw)
In-Reply-To: <4F0E940D.9050904@windriver.com>
On 01/12/2012 04:04 PM, wenzong fan wrote:
> On 01/12/2012 03:31 PM, Saul Wold wrote:
>> On 01/10/2012 11:34 PM, wenzong.fan@windriver.com wrote:
>>> From: Wenzong Fan<wenzong.fan@windriver.com>
>>>
>>> v2 updates:
>>>
>>> 1) Remove the special-casing for gcc, checking for any packages under
>>> 'tmp/work-shared';
>>>
>>> 2) Remove some bash-specific code, replase the '[[regular-expression]]'
>>> with isovalent 'grep' statement.
>>>
>>>
>> So how is this work different than that of Xiaofeng's doing the
>> tar_archive? Can these two be merged somehow? We also have
>> something called copyleft complaince, is this similar or somehow
>> different?
>
> They are a little similar but mostly are different, #1655 (Xiaofeng's)
> will need to export the source packages (such as *.tar, *.rpm ...) for
> using, Mark also commented the details at:
>
> http://bugzilla.pokylinux.org/show_bug.cgi?id=1655
>
> But the #1590 (mine) only archive the patched sources/build_scripts up
> for later checking.
And I think both the 'archive.bbclass' and 'copyleft_complaince.bbclass'
were designed for some license related issues, but the 'archive.bbclass'
will create snapshot for all sources and 'copyleft_complaince.bbclass'
will do dynamic checking for the licenses.
Thanks
Wenzong
>
> Thanks
> Wenzong
>
>>
>> We also have src_distribute.bbclass and sourcepkg.bbclass, seems like
>> we have a more ways to package up source code than we know what to do
>> with.
>>
>> Mark, we might want to sync up on this and figure out what we really
>> have and what's really needed here.
>>
>> Thanks
>> Sau!
>>
>>
>>
>>
>>> The following changes since commit
>>> 4a8a3c503fd896593b787c26edbe46a7324e494e:
>>> Richard Purdie (1):
>>> Revert "site/common-uclibc: Cache gl_cv_func_wcwidth_works"
>>>
>>> are available in the git repository at:
>>>
>>> git://git.pokylinux.org/poky-contrib wenzong/1590
>>> http://git.pokylinux.org/cgit.cgi/poky-contrib/log/?h=wenzong/1590
>>>
>>> Wenzong Fan (1):
>>> archive.bbclass: archive work directory
>>>
>>> meta/classes/archive.bbclass | 49
>>> ++++++++++++++++++++++++++++++++++++++++++
>>> 1 files changed, 49 insertions(+), 0 deletions(-)
>>> create mode 100644 meta/classes/archive.bbclass
>>>
>>>
>>> _______________________________________________
>>> Openembedded-core mailing list
>>> Openembedded-core@lists.openembedded.org
>>> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>>>
>>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
>
prev parent reply other threads:[~2012-01-12 8:32 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-11 7:34 [PATCH v2 0/1] archive.bbclass: archive work directory wenzong.fan
2012-01-11 7:34 ` [PATCH v2 1/1] " wenzong.fan
2012-01-12 7:31 ` [PATCH v2 0/1] " Saul Wold
2012-01-12 8:04 ` wenzong fan
2012-01-12 8:25 ` wenzong fan [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=4F0E98E5.3020302@windriver.com \
--to=wenzong.fan@windriver.com \
--cc=Xiaofeng.Yan@windriver.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=sgw@linux.intel.com \
/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