Poky Project Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Saul Wold <saul.wold@intel.com>
Cc: poky@yoctoproject.org
Subject: Re: [PATCH 0/1] check if lockfile is writable (bug 606 patch V2)
Date: Wed, 29 Dec 2010 20:26:53 +0000	[thread overview]
Message-ID: <1293654413.17519.9146.camel@rex> (raw)
In-Reply-To: <4D1B7784.6080604@intel.com>

On Wed, 2010-12-29 at 10:01 -0800, Saul Wold wrote:
> I still wonder about this.  If the DL_DIR is read-only, since it is a 
> shared environment (as example), when a fetch occurs, it may be for 
> different reasons.
> 
> A couple of examples are:
> 1) an upstream fetch was missed (world build, but different hardware)
> 2) a developer changed the version information
> 
> In cases like this we really do want to do the fetch, so how can we 
> handle that issue correctly, and not just fail and force the user to 
> re-download all the packages (which may not be possible).
> 
> One option I can think of is to add a "WRITABLE_DL_DIR" (losy name but 
> you get the idea) or something like that which if the DL_DIR is 
> read-only could be written to for the lock file and ultimately the fetch 
> of the missing upstream package.

DL_DIR *must* be writeable. We don't support the use case where it is
not. We handle readonly directory sources as part of the mirror
handling. It might be not a lot is written to DL_DIR, that is just fine.

I therefore agree with Ke's patch which errors if the directory is
writeable.

Cheers,

Richard





  reply	other threads:[~2010-12-29 20:27 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-29  9:54 [PATCH 0/1] check if lockfile is writable (bug 606 patch V2) Yu Ke
2010-12-29  9:54 ` [PATCH 1/1] bb.utils: check if lock file is writable, to fix bug 606 Yu Ke
2010-12-29 18:01 ` [PATCH 0/1] check if lockfile is writable (bug 606 patch V2) Saul Wold
2010-12-29 20:26   ` Richard Purdie [this message]
2010-12-30  2:19     ` Yu Ke
2010-12-30  9:29 ` 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=1293654413.17519.9146.camel@rex \
    --to=richard.purdie@linuxfoundation.org \
    --cc=poky@yoctoproject.org \
    --cc=saul.wold@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