From: Ulf Samuelsson <ulf_samuelsson@telia.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: Use of stamps in the source directory of openembedded-core
Date: Wed, 19 Oct 2011 10:17:51 +0200 [thread overview]
Message-ID: <4E9E87AF.70900@telia.com> (raw)
In-Reply-To: <4E9D8EC0.4030409@gmail.com>
2011-10-18 16:35, Khem Raj skrev:
> On 10/18/2011 1:18 AM, Ulf Samuelsson wrote:
>> After I have built openembedded-core, I notice that the source directory
>> is loaded with files: *.done.
>>
>
> they indicate successful download of a source tar.
>
Are you sure?
It does not look like the whole story to me.
I can see that for each source file, there is a *.done file,
but there are also a lot of *.done which seems to be related
to patches, and the patches are not present in the source directory.
Why are those files created?
What happens if two different packages have a patch with the same name?
>> Is this really a good idea?
>>
>> I tend to use a common source directory for multiple projects.
>>
>> Having stamps in the source directory, means that you let one
>> project affect the others.
>>
>
>
> _______________________________________________
> Openembedded-devel mailing list
> Openembedded-devel@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel
--
Best Regards
Ulf Samuelsson
next prev parent reply other threads:[~2011-10-19 8:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-18 8:18 Use of stamps in the source directory of openembedded-core Ulf Samuelsson
2011-10-18 14:35 ` Khem Raj
2011-10-19 8:17 ` Ulf Samuelsson [this message]
2011-10-19 8:38 ` Anders Darander
2011-10-19 8:45 ` Martin Jansa
2011-10-19 9:27 ` 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=4E9E87AF.70900@telia.com \
--to=ulf_samuelsson@telia.com \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.