Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Otavio Salvador <otavio.salvador@ossystems.com.br>
Cc: Patches and discussions about the oe-core layer
	<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 0/2] bitbake.conf: add GITHUB_GIT
Date: Fri, 31 Jul 2015 15:30:52 +0100	[thread overview]
Message-ID: <1438353052.22462.80.camel@linuxfoundation.org> (raw)
In-Reply-To: <CAP9ODKo=-GW32HqzO3ewzNi+YYL8U-Gcp8zAx9xKCs+vrYkb5w@mail.gmail.com>

On Thu, 2015-07-30 at 08:34 -0300, Otavio Salvador wrote:
> On Thu, Jul 30, 2015 at 5:32 AM, Olof Johansson <olof.johansson@axis.com> wrote:
> > Excerpts from Robert Yang's message of 2015-07-30 09:09:07 +0200:
> >> PREMIRRORS is for all the recipes/protocols ?
> >
> > No, PREMIRRORS is quite expressive, for instance:
> >
> > PREMIRRORS = " \
> >   https?$://downloads.example.org$/.*   http://mirror.example.com/ \n \
> > "
> >
> > This should only premirror downloads.example.com files, fetched via http
> > or https. See the bitbake fetcher's uri_replace method in
> > bitbake/lib/bb/fetch2/__init__.py for the implementation.
> 
> Yes, you can.
> 
> But the mirrors scheme allows for, for example, map it for git:// and
> https:// protocols without changing the recipes.
> 
> I am in favor of consistency here and having a unique var for github helps.

I came to review this as Ross pulled it into mut and I reached the same
conclusion as Olof here. We have PREMIRRORS, we can also exclude
networks from the fetcher and therefore have a ton of ways of rewriting
this already.

Yes, we do want standardisation, but all the urls look standardised to
me already. 

IMO, we want to see less of these global variables, not more. There once
was a time when they might have been useful but the fetcher is pretty
good about dealing with this now so lets not complicate this more than
we need to.

Cheers,

Richard




      reply	other threads:[~2015-07-31 14:31 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-29  9:11 [PATCH 0/2] bitbake.conf: add GITHUB_GIT Robert Yang
2015-07-29  9:11 ` [PATCH 1/2] " Robert Yang
2015-07-29  9:11 ` [PATCH 2/2] meta: git://github.com -> ${GITHUB_GIT} Robert Yang
2015-07-29 10:11 ` [PATCH 0/2] bitbake.conf: add GITHUB_GIT Paul Eggleton
2015-07-29 10:19   ` Robert Yang
2015-07-29 11:48     ` Olof Johansson
2015-07-29 16:27       ` Otavio Salvador
2015-07-30  1:51         ` Robert Yang
2015-07-30  7:04         ` Olof Johansson
2015-07-30  7:09           ` Robert Yang
2015-07-30  8:32             ` Olof Johansson
2015-07-30 11:34               ` Otavio Salvador
2015-07-31 14:30                 ` Richard Purdie [this message]

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=1438353052.22462.80.camel@linuxfoundation.org \
    --to=richard.purdie@linuxfoundation.org \
    --cc=openembedded-core@lists.openembedded.org \
    --cc=otavio.salvador@ossystems.com.br \
    /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