Openembedded Devel Discussions
 help / color / mirror / Atom feed
From: Joshua Lock <josh@linux.intel.com>
To: openembedded-devel@lists.openembedded.org
Subject: Re: How to prevent fetching?
Date: Wed, 31 Aug 2011 12:35:00 -0700	[thread overview]
Message-ID: <1314819305.2284.2.camel@scimitar> (raw)
In-Reply-To: <1314811518.1457.10.camel@DaveBeal-Ubuntu-laptop>

On Wed, 2011-08-31 at 11:25 -0600, Dave Beal wrote:
> My company is using OE to develop the embedded Linux infrastructure of a
> medical device.  The US government agency that approves such devices
> (FDA) requires that its source code be strictly controlled.  We would
> like to configure our OE installation to prevent the fetching of new
> source code except when we explicitly allow it.
> 
> Is there a way to accomplish this that doesn't require modifying all the
> individual .bb files?  Is there a global configuration option that would
> prevent fetching?  I've looked through the OE and Bitbake User Manuals,
> but haven't found an answer.

If you're using relatively recent BitBake and your metadata uses fetch2
(I don't know if oe.dev does, but oe-core is using fetch2) you can set
BB_NO_NETWORK="1" in a conf file somewhere.

Regards,
Joshua
-- 
Joshua Lock
        Yocto Project "Johannes factotum"
        Intel Open Source Technology Centre




  parent reply	other threads:[~2011-08-31 19:41 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-08-31 17:25 How to prevent fetching? Dave Beal
2011-08-31 19:20 ` Frans Meulenbroeks
2011-08-31 19:35 ` Joshua Lock [this message]
2011-08-31 21:18   ` Dave Beal
2011-08-31 22:30     ` Joshua Lock
2011-08-31 22:39       ` Dave Beal
2011-08-31 23:46         ` Gary Thomas

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=1314819305.2284.2.camel@scimitar \
    --to=josh@linux.intel.com \
    --cc=openembedded-devel@lists.openembedded.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox