Re: Write-protect $DL_DIR

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

On Tue, 2010-12-21 at 11:56 -0700, Gary Thomas wrote:
> On 12/21/2010 09:39 AM, Scott Garman wrote:
> > On 12/21/2010 07:45 AM, Gary Thomas wrote:
> >> In my quest for a well-packaged Poky that I can distribute
> >> to my customers, I'd like to give them a pre-populated $DL_DIR
> >> tree (also in response to those customers that have little or
> >> no net access). This would likely be in /opt/XYZ and practice
> >> would dictate that it be read-only.
> >>
> >> Sadly, this doesn't work. When I try to build Poky with a
> >> read-only $DL_DIR, it simply hangs on every 'fetch' step.
> >>
> >> Note: I could avoid this problem (although I think it's a
> >> bug even if it should never be experienced) by being able
> >> to easily provide source mirrors for the packages. So far,
> >> I've not figured out how to do this; I'd like to add my
> >> own mirror lists, similar to those in meta/classes/poky.bbclass
> >> Would this be a way forward? If so, how?
> >>
> >> Thanks for any ideas
> >
> > Hi Gary,
> >
> > Being able to do this is an important priority. Please file a bug to
> track it if there isn't a current workaround.
> 
> Done, bug #606.

Sorry but this isn't what is being asked and I don't think that bug is
reasonable. DL_DIR needs to be writeable. You can implement a readonly
mirror just fine without requiring that so we have what I think is a
very reasonable way to solve the problem.

> I'll also look at Richard's new support for MIRRORS/PREMIRRORS
> to see how to make it work for my environment.

Please do this and report back on how you get one. I'm fine with
documenting this and making things clearer. Turning DL_DIR into some new
mirror and having a new writable area for state information isn't the
right way to solve this problem though when we have mirror handling for
exactly this kind of use case already.

Cheers,

Richard