From: Gary Thomas <gary@mlbassoc.com>
To: Richard Purdie <richard.purdie@linuxfoundation.org>
Cc: poky@yoctoproject.org
Subject: Re: Write-protect $DL_DIR
Date: Tue, 21 Dec 2010 15:34:16 -0700 [thread overview]
Message-ID: <4D112B68.10303@mlbassoc.com> (raw)
In-Reply-To: <1292966869.25087.6574.camel@rex>
On 12/21/2010 02:27 PM, Richard Purdie wrote:
> 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.
I understand that these are really [now] two separate things.
I had been trying to use $DL_DIR as a pure mirror, but your change
of today will make that no longer necessary.
I went ahead and filed the bug about a read-only $DL_DIR because
it causes the build to hang/build silently which could cause confusion.
The build should either fail at fetch time with a message or be
sanity checked.
I've tried your changes and they solve my problem well, thanks.
--
------------------------------------------------------------
Gary Thomas | Consulting for the
MLB Associates | Embedded world
------------------------------------------------------------
next prev parent reply other threads:[~2010-12-21 22:34 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-21 15:45 Write-protect $DL_DIR Gary Thomas
2010-12-21 16:02 ` Eric Bénard
2010-12-21 16:39 ` Scott Garman
2010-12-21 18:56 ` Gary Thomas
2010-12-21 21:27 ` Richard Purdie
2010-12-21 22:34 ` Gary Thomas [this message]
2010-12-22 14:51 ` Gary Thomas
2010-12-22 15:24 ` Gary Thomas
2010-12-23 14:08 ` Gary Thomas
2010-12-21 16:44 ` Richard Purdie
2010-12-21 16:52 ` Gary Thomas
2010-12-21 17:40 ` 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=4D112B68.10303@mlbassoc.com \
--to=gary@mlbassoc.com \
--cc=poky@yoctoproject.org \
--cc=richard.purdie@linuxfoundation.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.