From: Saul Wold <sgw@linux.intel.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 2/7] archiver.bbclass: New bbclass for archiving sources, patches, logs and scripts
Date: Tue, 20 Mar 2012 07:41:29 -0700 [thread overview]
Message-ID: <4F689719.6090100@linux.intel.com> (raw)
In-Reply-To: <CAE4k23-U8gr0_B9jyZb8qXhwQQZLFA6O20PdG7j1SohpdQdx6Q@mail.gmail.com>
On 03/20/2012 03:00 AM, Anders Darander wrote:
> On Tue, Mar 20, 2012 at 10:49, Xiaofeng Yan<xiaofeng.yan@windriver.com> wrote:
>> On 2012年03月20日 17:40, Xiaofeng Yan wrote:
>>>
>>> On 2012年03月20日 16:07, Koen Kooi wrote:
>>>>
>>>> Op 20 mrt. 2012, om 06:50 heeft Xiaofeng Yan het volgende geschreven:
>>>>
>>>>> On 2012年03月20日 05:04, Saul Wold wrote:
>>>>>>
>>>>>> On 03/15/2012 11:23 PM, Xiaofeng Yan wrote:
>>>>>>>
>>>>>>> From: Xiaofeng Yan<xiaofeng.yan@windriver.com>
>>>>>>>
>>>>>> Why do you rebuild the tarball here are rename it instead of just
>>>>>> copying the original tarball?
>>>>>>
>>>>> because many packages come from non-tarball and they could be git
>>>>> sources , So I archive these sources after do_unpack.
>>>>
>>>> But if you have the original tarball and reuse it, you'll get the warm
>>>> fuzzy feeling of matching checksums.
>>>
>>> So How about renaming archive-original-source to
>>> archive-prepatched-source?
>>
>> Hi Saul,
>>
>> Or I can add a new functions to get tarball from downloads if have tarball
>> and archive source codes directory if have directory without tarball.
>> Do you think it is necessary for us to add this function?
>
> I'd say that this is a change that should be made. If nothing else,
> just to get the assurance that the archived tarball's are the same as
> the ones that was used to build the system. (This is beneficial both
> when it comes to using the archived tarballs for rebuilding the
> system, as well as for ensuring licence compliance).
>
I agree here, as Koen also pointed out, it will have matching checksums.
As to the name of the tarball, again best to keep it named the same as
the original tarball.
Sau!
> /Anders
>
> _______________________________________________
> 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-20 14:50 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-16 6:23 [PATCH 0/7] Realize archiving functions Xiaofeng Yan
2012-03-16 6:23 ` [PATCH 1/7] package_rpm: Add srpm function to this bbclass Xiaofeng Yan
2012-03-16 6:23 ` [PATCH 2/7] archiver.bbclass: New bbclass for archiving sources, patches, logs and scripts Xiaofeng Yan
2012-03-19 21:04 ` Saul Wold
2012-03-20 5:50 ` Xiaofeng Yan
2012-03-20 8:07 ` Koen Kooi
2012-03-20 9:40 ` Xiaofeng Yan
2012-03-20 9:49 ` Xiaofeng Yan
2012-03-20 10:00 ` Anders Darander
2012-03-20 14:41 ` Saul Wold [this message]
2012-03-21 6:39 ` Xiaofeng Yan
2012-03-16 6:23 ` [PATCH 3/7] archive-patched-source.bbclass: Archive patched source Xiaofeng Yan
2012-03-16 6:23 ` [PATCH 4/7] archive-configured-source.bbclass: Archive configured source Xiaofeng Yan
2012-03-16 6:23 ` [PATCH 5/7] archive-original-source.bbclass: Archive original source Xiaofeng Yan
2012-03-16 6:23 ` [PATCH 6/7] local.conf.sample: Add set for archiving packages Xiaofeng Yan
2012-03-16 6:23 ` [PATCH 7/7] sourcepkg, src_distribute, src_distribute_local: remove three bbclass Xiaofeng Yan
-- strict thread matches above, loose matches on Subject: below --
2012-03-13 12:52 [PATCH 0/7] Realize archiving functions Xiaofeng Yan
2012-03-13 12:52 ` [PATCH 2/7] archiver.bbclass: New bbclass for archiving sources, patches, logs and scripts Xiaofeng Yan
2012-03-14 2:57 ` Saul Wold
2012-03-14 12:30 ` 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=4F689719.6090100@linux.intel.com \
--to=sgw@linux.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