On Fri, 17 Jul 2015 08:20:48 -0600 Mats Wichmann <[email protected]> said:

> On 07/17/15 03:45, Leon Anavi wrote:
> > Hi Carsten, Andreas,
> > 
> > On 17.07.2015 04:03, Carsten Haitzler (The Rasterman) wrote:
> >> it's time we dump gbs. it's far too limiting. we have to move to a pure
> >> cross-build ala yocto. debugging qemu binfmt emulation is a nightmare
> >> - it's
> >> pretty close to impossible, and an insane time-sink.
> > +1
> > 
> > On 17.07.2015 12:06, Andreas Brauchli wrote:
> >> On Fre, 2015-07-17 at 12:19 +0900, Carsten Haitzler wrote:
> >>> which is impossible to use thanks to company firewalls basically
> >>> blocking
> >>> things like git protocol - would have to modify every .bb file and
> >>> move to
> >>> http - if it exists for that git repo every git checkout from
> >>> tizen.org as it
> >>> has to go via ssh, requires a firewall exception...
> >>>
> >>> suffice to say yocto is flakey-custom-corporate-it-unfriendly. i'm
> >>> not sinking
> >>> more time into it and fighting with it, firewalls, proxies, ssh etc.
> >>>
> >>> :(
> >> Good to hear that this is registered.
> >> not just yocto, also gerrit and the gbs build examples all use ssh or
> >> git ports
> >>
> >> The whole public infrastructure should really be more accessible to
> >> corporate setups!
> > This can be fixed easily by explicitly specifying HTTPS as the protocol
> > that should be used for fetching source code from Git at the SRC_URI of
> > each Yocto recipe for Tizen.
> 
> right, it *looks* to me like it's not horribly complex, you make the
> lines look like (sample from bitbake docs):
> 
> git://git.yoctoproject.org/git/poky;protocol=http
> 
> or https, or whatever it needs to be.
> 
> 
> I didn't run into this because I ran my experiments from a place that
> wasn't firewalled either.

indeed. it's just a lot of little pieces of work. testing. repeat. :)

-- 
Carsten Haitzler (The Rasterman) <[email protected]>
_______________________________________________
General mailing list
[email protected]
https://lists.tizen.org/listinfo/general

Reply via email to