[bitbake-devel] Allow access to specific git server while BB_FETCH_PREMIRRORONLY ="1"

[Paul Eggleton]

Hi Scott,

I didn't add you to CC because I'd hoped it would be someone other than you or 
me this time :)

(Not that I intended to poke the people who were on CC to add it either 
though.)

Cheers,
Paul

On Monday 15 June 2015 12:57:34 Rifenbark, Scott M wrote:
> Someone?  Ha.
> 
> >-----Original Message-----
> >From: bitbake-devel-bounces at lists.openembedded.org [mailto:bitbake-
> >devel-bounces at lists.openembedded.org] On Behalf Of Paul Eggleton
> >Sent: Monday, June 15, 2015 5:56 AM
> >To: bitbake-devel at lists.openembedded.org
> >Cc: Christopher Larson
> >Subject: Re: [bitbake-devel] Allow access to specific git server while
> >BB_FETCH_PREMIRRORONLY ="1"
> >
> >On Sunday 14 June 2015 23:43:54 Bernhard Reutner-Fischer wrote:
> >> On June 12, 2015 3:04:17 PM GMT+02:00, Christopher Larson
> >
> ><clarson at kergoth.com> wrote:
> >> >On Fri, Jun 12, 2015 at 7:47 AM, Bach, Pascal
> >> ><pascal.bach at siemens.com>
> >> >
> >> >wrote:
> >> >> I was wondering if there is a way to allow access to specific urls
> >> >
> >> >even if
> >> >
> >> >> BB_NO_NETWORK or BB_FETCH_PREMIRRORONLY is set.
> >> >> 
> >> >> The use case I have at hand it that we want to fetch all 3rd party
> >> >
> >> >sources
> >> >
> >> >> from a HTTP premirror we have internally. Except for some packages
> >> >
> >> >that
> >> >
> >> >> are hosted on a git server where we would like bitbake to always
> >> >
> >> >fetch from
> >> >
> >> >> there (no tarball on the pre mirror).
> >> >> 
> >> >> I tried:
> >> >> PREMIRROR_prepend = "git at local/foo.git git at local/foo.git \n"
> >> >> 
> >> >> 
> >> >> But this doesn't seem to work.
> >> >> 
> >> >> Is there way to achieve this with the current PREMIRROR variable?
> >> >> Or
> >> >
> >> >is
> >> >
> >> >> this functionality currently missing?
> >> >
> >> >See the recently added BB_TRUSTED_NETWORK variable.
> >> 
> >> I hope the v3 with BB_ALLOWED_NETWORKS was applied instead but
> >
> >cannot
> >
> >> currently check.
> >
> >Looking at master, it was - BB_ALLOWED_NETWORKS is indeed the new
> >variable for this.
> >
> >(Speaking of which, someone needs to add that to the docs...)



-- 

Paul Eggleton
Intel Open Source Technology Centre