From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: Jon Szymaniak <jon.szymaniak@gmail.com>
Cc: yocto@yoctoproject.org
Subject: Re: Disabling PREMIRRORS and upstream sources
Date: Wed, 12 Dec 2012 16:48:58 +0000 [thread overview]
Message-ID: <2131314.OQZPzJsPrp@helios> (raw)
In-Reply-To: <CANge7vWPf-sqGH_sdoVHoLvnpK_wPXC_QBAkUG2dEvMUzz99UQ@mail.gmail.com>
On Wednesday 12 December 2012 11:32:39 Jon Szymaniak wrote:
> Just to make sure I'm understanding this... so when I place PREMIRRORS = ""
> in a recipe, I see that it doesn't affect the associated variables in other
> recipes.
>
> Is this because I'm inherently setting up PREMIRRORS_${PN}, which is
> initialized with the PREMIRROR defaults (and what was appended and
> prepended in the local.conf)?
When you set a variable within a recipe it's setting it just within the
context of that recipe, so there's no way for it to affect other recipes.
> I'm also guessing that touching PREMIRRORS and MIRRORS within recipes
> is generally a bad practice. I'd be curious to hear if my use case
> sounds totally
> wacky, as I'm still very much getting up to speed on Yocto/OE and best
> practices.
I guess it's not unreasonable to want to avoid touching anything external when
building something internal; but you're right as a general practice this is
something we would not do in published recipes.
Cheers,
Paul
--
Paul Eggleton
Intel Open Source Technology Centre
next prev parent reply other threads:[~2012-12-12 16:49 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-03 15:19 Disabling PREMIRRORS and upstream sources Jon Szymaniak
2012-12-11 21:09 ` Rifenbark, Scott M
2012-12-12 4:26 ` Jon Szymaniak
2012-12-12 12:42 ` Rifenbark, Scott M
2012-12-12 15:05 ` Rifenbark, Scott M
2012-12-12 16:32 ` Jon Szymaniak
2012-12-12 16:48 ` Paul Eggleton [this message]
2012-12-12 17:23 ` Rifenbark, Scott M
2012-12-12 12:52 ` Paul Eggleton
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=2131314.OQZPzJsPrp@helios \
--to=paul.eggleton@linux.intel.com \
--cc=jon.szymaniak@gmail.com \
--cc=yocto@yoctoproject.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.