Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Manjukumar Harthikote Matha <MANJUKUM@xilinx.com>,
	Bhargava Sreekantappa Gayathri <BSREEKAN@xilinx.com>,
	"openembedded-core@lists.openembedded.org"
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH] own-mirrors.bbclass: Change prepend to append
Date: Fri, 09 Mar 2018 11:04:06 -0800	[thread overview]
Message-ID: <1520622246.10851.146.camel@linuxfoundation.org> (raw)
In-Reply-To: <BY2PR02MB347E13EAB004D3AB8E628A0B9DE0@BY2PR02MB347.namprd02.prod.outlook.com>

On Fri, 2018-03-09 at 17:56 +0000, Manjukumar Harthikote Matha wrote:
> 
> > 
> > -----Original Message-----
> > From: Richard Purdie [mailto:richard.purdie@linuxfoundation.org]
> > Sent: Friday, March 09, 2018 5:27 AM
> > To: Bhargava Sreekantappa Gayathri <BSREEKAN@xilinx.com>;
> > openembedded-
> > core@lists.openembedded.org; Manjukumar Harthikote Matha
> > <MANJUKUM@xilinx.com>
> > Subject: Re: [OE-core] [PATCH] own-mirrors.bbclass: Change prepend
> > to append
> > 
> > On Thu, 2018-03-08 at 17:49 -0800, Bhargava Sreekantappa Gayathri
> > wrote:
> > > 
> > > If BB_NO_NETWORK is set to 1, and local download directory is
> > > added as
> > > PREMIRRORS_prepend in conf file, PREMIRRORS variable will have
> > > SOURCE_MIRROR_URL as the first url. This causes build to fail as
> > > network access is diabled. PREMIRRORS should be appended here so
> > > that
> > > a prepend in other layers/conf files takes precedence.
> > > 
> > > Signed-off-by: Bhargava Sreekantappa Gayathri
> > > <bhargava.sreekantappa-
> > > gayathri@xilinx.com>
> > > Signed-off-by: Manjukumar Matha <manjukumar.harthikote-matha@xili
> > > nx.c
> > > om>
> > > ---
> > >  meta/classes/own-mirrors.bbclass | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > I think this patch just moves the problem, you could easily have a
> > file:/// url
> > as SOURCE_MIRROR_URL and a network address in your other layer in
> > which case
> > your patch would break things...
> > 
> 
> Agreed.
> I think the better fix would be to go through the entire available
> list in PREMIRRORS skipping http or https  (since BB_NO_NETWORK is
> set) and then fail if we cannot get the required file.

Agreed, we just need to ensure users see a mention that BB_NO_NETWORK
is set in those failure modes.

Cheers,

Richard


  reply	other threads:[~2018-03-09 19:04 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-09  1:49 [PATCH] own-mirrors.bbclass: Change prepend to append Bhargava Sreekantappa Gayathri
2018-03-09 13:26 ` Richard Purdie
2018-03-09 17:56   ` Manjukumar Harthikote Matha
2018-03-09 19:04     ` Richard Purdie [this message]
2018-03-20 20:26     ` Bhargava Sreekantappa Gayathri
  -- strict thread matches above, loose matches on Subject: below --
2018-03-09  1:54 Bhargava Sreekantappa Gayathri
2018-03-09  1:06 Bhargava Sreekantappa Gayathri

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=1520622246.10851.146.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=BSREEKAN@xilinx.com \
    --cc=MANJUKUM@xilinx.com \
    --cc=openembedded-core@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