From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: sharing DL_DIR?
Date: Thu, 23 Feb 2012 20:41:03 +0000 [thread overview]
Message-ID: <1330029663.32110.85.camel@ted> (raw)
In-Reply-To: <4F46A346.3050809@palm.com>
On Thu, 2012-02-23 at 12:36 -0800, Rich Pixley wrote:
> On 2/23/12 12:11 , Richard Purdie wrote:
> > On Thu, 2012-02-23 at 11:21 -0800, Rich Pixley wrote:
> >> On 2/23/12 02:16 , Richard Purdie wrote:
> >>> On Wed, 2012-02-22 at 16:47 -0800, Rich Pixley wrote:
> >>>> What happens if two separate bitbake invocations both simultaneously
> >>>> attempt to download the same file?
> >>> The first will download it, the second will wait for it to finish, then
> >>> both will continue with the downloaded file.
> >> How does the second know that the first is in progress?
> > It won't be able to take the lock and the done stamp file doesn't exist
> > yet.
> What lock?
>
> I've just read through lib/bb/fetch2/__init__.py but I'm not seeing a
> lock. What am I missing?
Try searching that file for expressions like "lock" and "lockfile" ;-)
Cheers,
Richard
next prev parent reply other threads:[~2012-02-23 20:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-22 23:33 sharing DL_DIR? Rich Pixley
2012-02-22 23:39 ` Tom King
2012-02-22 23:41 ` Christopher Larson
2012-02-23 0:47 ` Rich Pixley
2012-02-23 10:16 ` Richard Purdie
2012-02-23 19:21 ` Rich Pixley
2012-02-23 20:11 ` Richard Purdie
2012-02-23 20:36 ` Rich Pixley
2012-02-23 20:41 ` Richard Purdie [this message]
2012-02-22 23:41 ` Saul Wold
2012-02-23 0:50 ` Rich Pixley
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=1330029663.32110.85.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