Disabling PREMIRRORS and upstream sources

Disabling PREMIRRORS and upstream sources

[Jon Szymaniak]

Is there a simple way to disable the use of PREMIRRORS and MIRRORS
within a recipe?

(Perhaps the answer here might be worth mentioning in Section 12.23 of the
Poky Reference  Manual?)

My use case for this is the situation where the code hasn't been released yet,
so there's no point in checking mirrors.

Thank you,
Jon

Re: Disabling PREMIRRORS and upstream sources

[Rifenbark, Scott M]

Isn't this set up in the local.conf file for global use?  Also, Jon, what documentation are you referring to here?  Are you looking at the latest Yocto Project documentation (e.g. http://www.yoctoproject.org/docs/1.4/poky-ref-manual/poky-ref-manual.html for the Yocto Project Reference Manual?).

Scott

>-----Original Message-----
>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>bounces@yoctoproject.org] On Behalf Of Jon Szymaniak
>Sent: Monday, December 03, 2012 7:19 AM
>To: yocto@yoctoproject.org
>Subject: [yocto] Disabling PREMIRRORS and upstream sources
>
>Is there a simple way to disable the use of PREMIRRORS and MIRRORS
>within a recipe?
>
>(Perhaps the answer here might be worth mentioning in Section 12.23 of
>the
>Poky Reference  Manual?)
>
>My use case for this is the situation where the code hasn't been
>released yet,
>so there's no point in checking mirrors.
>
>Thank you,
>Jon
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto

Re: Disabling PREMIRRORS and upstream sources

[Jon Szymaniak]

>>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>>bounces@yoctoproject.org] On Behalf Of Jon Szymaniak
>>Sent: Monday, December 03, 2012 7:19 AM
>>To: yocto@yoctoproject.org
>>Subject: [yocto] Disabling PREMIRRORS and upstream sources
>>
>>Is there a simple way to disable the use of PREMIRRORS and MIRRORS
>>within a recipe?
>>
>>(Perhaps the answer here might be worth mentioning in Section 12.23 of
>>the
>>Poky Reference  Manual?)
>>
>>My use case for this is the situation where the code hasn't been
>>released yet,
>>so there's no point in checking mirrors.
>>
>>Thank you,
>>Jon


> Isn't this set up in the local.conf file for global use?

In the manual I see that there are indeed global options, configured via
local.conf.

However, I'm wondering if there's a way to denote that PREMIRRORS and MIRRORS
should not be used for a *specific recipe* (i.e., only attempt to fetch via
what's provided in SRC_URI, and still use the mirrors for other recipes).

Perhaps this is a wacky thing to want to do. I just figured there's no sense
in hitting all those 404's if I know the code associated with a specific
recipe isn't on any of the standard mirrors.

> Also, Jon, what documentation
> are you referring to here?  Are you looking at the latest Yocto Project
> documentation (e.g. http://www.yoctoproject.org/docs/1.4/poky-ref-manual/poky-ref-manual.html
> for the Yocto Project Reference Manual?).

I think I may have actually been looking at an old manual version, but yes,
that'd the documentation I was referring to. It seemed that 12.23, "How does
the OpenEmbedded build system obtain source code..." seemed the most relevant
to my question.

Thanks!
Jon

Re: Disabling PREMIRRORS and upstream sources

[Rifenbark, Scott M]

Hi Jon, 

Thanks for the clarification on which manual release you were looking at.  I am the technical writer for the project so hopefully someone from the team will address the technical aspect of you issue.  If there is a way to disable these within a specific recipe then I can get that information into the documentation.  

Does anyone know if this is possible and how to do it?

Scott

>-----Original Message-----
>From: Jon Szymaniak [mailto:jon.szymaniak@gmail.com]
>Sent: Tuesday, December 11, 2012 8:26 PM
>To: Rifenbark, Scott M
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] Disabling PREMIRRORS and upstream sources
>
>>>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>>>bounces@yoctoproject.org] On Behalf Of Jon Szymaniak
>>>Sent: Monday, December 03, 2012 7:19 AM
>>>To: yocto@yoctoproject.org
>>>Subject: [yocto] Disabling PREMIRRORS and upstream sources
>>>
>>>Is there a simple way to disable the use of PREMIRRORS and MIRRORS
>>>within a recipe?
>>>
>>>(Perhaps the answer here might be worth mentioning in Section 12.23 of
>>>the
>>>Poky Reference  Manual?)
>>>
>>>My use case for this is the situation where the code hasn't been
>>>released yet,
>>>so there's no point in checking mirrors.
>>>
>>>Thank you,
>>>Jon
>
>
>> Isn't this set up in the local.conf file for global use?
>
>In the manual I see that there are indeed global options, configured via
>local.conf.
>
>However, I'm wondering if there's a way to denote that PREMIRRORS and
>MIRRORS
>should not be used for a *specific recipe* (i.e., only attempt to fetch
>via
>what's provided in SRC_URI, and still use the mirrors for other
>recipes).
>
>Perhaps this is a wacky thing to want to do. I just figured there's no
>sense
>in hitting all those 404's if I know the code associated with a specific
>recipe isn't on any of the standard mirrors.
>
>> Also, Jon, what documentation
>> are you referring to here?  Are you looking at the latest Yocto
>Project
>> documentation (e.g. http://www.yoctoproject.org/docs/1.4/poky-ref-
>manual/poky-ref-manual.html
>> for the Yocto Project Reference Manual?).
>
>I think I may have actually been looking at an old manual version, but
>yes,
>that'd the documentation I was referring to. It seemed that 12.23, "How
>does
>the OpenEmbedded build system obtain source code..." seemed the most
>relevant
>to my question.
>
>Thanks!
>Jon

Re: Disabling PREMIRRORS and upstream sources

[Rifenbark, Scott M]

Jon, 

Here is a response from Paul Eggleton that I got for the question via a separate email thread:

> Is there a simple way to disable the use of PREMIRRORS and MIRRORS 
> within a recipe?
> 
> (Perhaps the answer here might be worth mentioning in Section 12.23 of 
> the Poky Reference  Manual?)
> 
> My use case for this is the situation where the code hasn't been 
> released yet, so there's no point in checking mirrors.

I guess the easiest thing would be just to set PREMIRRORS and MIRRORS to "" in the recipe.

Cheers,
Paul

Scott

>-----Original Message-----
>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>bounces@yoctoproject.org] On Behalf Of Rifenbark, Scott M
>Sent: Wednesday, December 12, 2012 4:43 AM
>To: Jon Szymaniak
>Cc: yocto@yoctoproject.org
>Subject: Re: [yocto] Disabling PREMIRRORS and upstream sources
>
>Hi Jon,
>
>Thanks for the clarification on which manual release you were looking
>at.  I am the technical writer for the project so hopefully someone from
>the team will address the technical aspect of you issue.  If there is a
>way to disable these within a specific recipe then I can get that
>information into the documentation.
>
>Does anyone know if this is possible and how to do it?
>
>Scott
>
>>-----Original Message-----
>>From: Jon Szymaniak [mailto:jon.szymaniak@gmail.com]
>>Sent: Tuesday, December 11, 2012 8:26 PM
>>To: Rifenbark, Scott M
>>Cc: yocto@yoctoproject.org
>>Subject: Re: [yocto] Disabling PREMIRRORS and upstream sources
>>
>>>>From: yocto-bounces@yoctoproject.org [mailto:yocto-
>>>>bounces@yoctoproject.org] On Behalf Of Jon Szymaniak
>>>>Sent: Monday, December 03, 2012 7:19 AM
>>>>To: yocto@yoctoproject.org
>>>>Subject: [yocto] Disabling PREMIRRORS and upstream sources
>>>>
>>>>Is there a simple way to disable the use of PREMIRRORS and MIRRORS
>>>>within a recipe?
>>>>
>>>>(Perhaps the answer here might be worth mentioning in Section 12.23
>of
>>>>the
>>>>Poky Reference  Manual?)
>>>>
>>>>My use case for this is the situation where the code hasn't been
>>>>released yet,
>>>>so there's no point in checking mirrors.
>>>>
>>>>Thank you,
>>>>Jon
>>
>>
>>> Isn't this set up in the local.conf file for global use?
>>
>>In the manual I see that there are indeed global options, configured
>via
>>local.conf.
>>
>>However, I'm wondering if there's a way to denote that PREMIRRORS and
>>MIRRORS
>>should not be used for a *specific recipe* (i.e., only attempt to fetch
>>via
>>what's provided in SRC_URI, and still use the mirrors for other
>>recipes).
>>
>>Perhaps this is a wacky thing to want to do. I just figured there's no
>>sense
>>in hitting all those 404's if I know the code associated with a
>specific
>>recipe isn't on any of the standard mirrors.
>>
>>> Also, Jon, what documentation
>>> are you referring to here?  Are you looking at the latest Yocto
>>Project
>>> documentation (e.g. http://www.yoctoproject.org/docs/1.4/poky-ref-
>>manual/poky-ref-manual.html
>>> for the Yocto Project Reference Manual?).
>>
>>I think I may have actually been looking at an old manual version, but
>>yes,
>>that'd the documentation I was referring to. It seemed that 12.23, "How
>>does
>>the OpenEmbedded build system obtain source code..." seemed the most
>>relevant
>>to my question.
>>
>>Thanks!
>>Jon
>_______________________________________________
>yocto mailing list
>yocto@yoctoproject.org
>https://lists.yoctoproject.org/listinfo/yocto

Re: Disabling PREMIRRORS and upstream sources

[Jon Szymaniak]

>>Hi Jon,
>>
>>Thanks for the clarification on which manual release you were looking
>>at.  I am the technical writer for the project so hopefully someone from
>>the team will address the technical aspect of you issue.  If there is a
>>way to disable these within a specific recipe then I can get that
>>information into the documentation.
>>
>>Does anyone know if this is possible and how to do it?
>>
>>Scott
>
> I guess the easiest thing would be just to set PREMIRRORS and MIRRORS to
> "" in the recipe.
>
> Cheers,
> Paul
>
> Scott
>

Scott and Paul,

Thank you both very much for your time and help!

I confirmed this does indeed work.

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)?

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.


Many thanks,
Jon

Re: Disabling PREMIRRORS and upstream sources

[Paul Eggleton]

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

Re: Disabling PREMIRRORS and upstream sources

[Rifenbark, Scott M]

If this is something we would not encourage in a published recipe, then it is questionable as to documenting this simple way.  Or, perhaps, document it with the caveat that it is not something you would normally do?

Scott

>-----Original Message-----
>From: Paul Eggleton [mailto:paul.eggleton@linux.intel.com]
>Sent: Wednesday, December 12, 2012 8:49 AM
>To: Jon Szymaniak
>Cc: Rifenbark, Scott M; yocto@yoctoproject.org
>Subject: Re: [yocto] Disabling PREMIRRORS and upstream sources
>
>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

Re: Disabling PREMIRRORS and upstream sources

[Paul Eggleton]

On Monday 03 December 2012 10:19:00 Jon Szymaniak wrote:
> Is there a simple way to disable the use of PREMIRRORS and MIRRORS
> within a recipe?
> 
> (Perhaps the answer here might be worth mentioning in Section 12.23 of the
> Poky Reference  Manual?)
> 
> My use case for this is the situation where the code hasn't been released
> yet, so there's no point in checking mirrors.

I guess the easiest thing would be just to set PREMIRRORS and MIRRORS to "" in 
the recipe.

Cheers,
Paul

-- 

Paul Eggleton
Intel Open Source Technology Centre