Re: [PATCH 0/1] check if lockfile is writable (bug 606 patch V2)

[Richard Purdie <richard.purdie@linuxfoundation.org>]

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