Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Cc: ulf@emagii.com
Subject: Re: Possible stale tags in the download directory
Date: Wed, 07 Dec 2011 15:00:54 +0000	[thread overview]
Message-ID: <1323270054.30601.26.camel@ted> (raw)
In-Reply-To: <3741284.XQAanrv0Ii@helios>

On Wed, 2011-12-07 at 14:37 +0000, Paul Eggleton wrote:
> On Wednesday 07 December 2011 15:30:38 Ulf Samuelsson wrote:
> > Richard says that if the *.done file is there, then the checksum is not
> > calculated.
> > Or that is at least how I interpret his comment.
> > 
> > If the check is always there, why the tag?
> 
> That's not what my reading of the bitbake source says. 
> bitbake/lib/bb/fetch2/__init__.py contains the only references to .done files 
> and all it does is make sure the done file gets "touched" whenever a fetch for 
> the associated file occurs; it does not otherwise check for its existence.

It does two things, one is an activity marker useful for seeing whether
files are in active use and the second is for the checksum calculation
which only ever happens once after download due to the file (see
verify_checksum() in that file).

Cheers,

Richard




  reply	other threads:[~2011-12-07 15:07 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-07  8:27 Possible stale tags in the download directory Ulf Samuelsson
2011-12-07  9:16 ` Richard Purdie
2011-12-07 11:27   ` Ulf Samuelsson
2011-12-07 12:00     ` Koen Kooi
2011-12-07 14:30       ` Ulf Samuelsson
2011-12-07 14:37         ` Paul Eggleton
2011-12-07 15:00           ` Richard Purdie [this message]
2011-12-07 21:43             ` Khem Raj
2011-12-07 23:46               ` Ulf Samuelsson
2011-12-07 15:04     ` Richard Purdie

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=1323270054.30601.26.camel@ted \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=ulf@emagii.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