Re: [yocto] Ignoring Fetch errors for optional source.

> On Dec 7, 2016, at 5:00 AM, Beth 'pidge' Flanagan wrote: > > I've an odd use case that I wonder if anyone has a work around/way of > doing it. > > I've a client who has contractors who can't have access to a certain > segment of the code base. So for example, a recipe

Re: [yocto] Ignoring Fetch errors for optional source.

On Wed, Dec 7, 2016 at 5:13 AM, Beth 'pidge' Flanagan wrote: > > Yeah, unfortunately, people don't neccessarily know they're special if you > get my meaning. > > One way we've been trying this is like so: > > try: > fetcher = bb.fetch2.Fetch(extra_uri, d) >

Re: [yocto] Ignoring Fetch errors for optional source.

On Wed, 2016-12-07 at 13:08 +, Burton, Ross wrote: > > On 7 December 2016 at 13:00, Beth 'pidge' Flanagan > om> wrote: > > I've an odd use case that I wonder if anyone has a work around/way > > of > > doing it. > > > > I've a client who has contractors who can't have access to a > > certain

Re: [yocto] Ignoring Fetch errors for optional source.

On 7 December 2016 at 13:00, Beth 'pidge' Flanagan wrote: > I've an odd use case that I wonder if anyone has a work around/way of > doing it. > > I've a client who has contractors who can't have access to a certain > segment of the code base. So for example, a recipe will

[yocto] Ignoring Fetch errors for optional source.

I've an odd use case that I wonder if anyone has a work around/way of doing it. I've a client who has contractors who can't have access to a certain segment of the code base. So for example, a recipe will have a SRC_URI for the main bit that everyone has access to, but an extra src_uri that some