All of lore.kernel.org
 help / color / mirror / Atom feed
From: Gary Thomas <gary@mlbassoc.com>
To: Poky <poky@lists.pokylinux.org>
Subject: Write-protect $DL_DIR
Date: Tue, 21 Dec 2010 08:45:12 -0700	[thread overview]
Message-ID: <4D10CB88.4040308@mlbassoc.com> (raw)

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

-- 
------------------------------------------------------------
Gary Thomas                 |  Consulting for the
MLB Associates              |    Embedded world
------------------------------------------------------------


             reply	other threads:[~2010-12-21 15:45 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-21 15:45 Gary Thomas [this message]
2010-12-21 16:02 ` Write-protect $DL_DIR 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
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=4D10CB88.4040308@mlbassoc.com \
    --to=gary@mlbassoc.com \
    --cc=poky@lists.pokylinux.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.