| Summary: | [jhbuild] Make jhbuild modules use https protocol instead of git | ||||||
|---|---|---|---|---|---|---|---|
| Product: | WebKit | Reporter: | Vivek Galatage <vivekg> | ||||
| Component: | Tools / Tests | Assignee: | Vivek Galatage <vivekg> | ||||
| Status: | NEW --- | ||||||
| Severity: | Normal | CC: | laszlo.gombos, mrobinson, ostap73, pnormand | ||||
| Priority: | P2 | ||||||
| Version: | 528+ (Nightly build) | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Attachments: |
|
||||||
|
Description
Vivek Galatage
2014-08-03 22:59:38 PDT
Created attachment 235964 [details]
Patch
Have you asked your network admins about this? Perhaps there's a less invasive way to use http instead of git by locally configuring your jhbuild setup? If possible I'd like to keep using git protocol by default because it's more efficient, see also http://git-scm.com/book/en/Git-on-the-Server-The-Protocols (In reply to comment #2) > Have you asked your network admins about this? > Yes and the IT dept is saying it will not be enabled for git as such. > Perhaps there's a less invasive way to use http instead of git by locally configuring your jhbuild setup? Any pointers on how to do it? Also is there a way to specifiy multiple URLs (fallback ones) in jhbuild.modules? This way we could always keep the first one to be git one and then https one based on priority and availability. Have you tried this approach? http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/ (In reply to comment #4) > Have you tried this approach? > > http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/ Sure, I will try this tomorrow once in office. Thank you. (In reply to comment #5) > (In reply to comment #4) > > Have you tried this approach? > > > > http://www.emilsit.net/blog/archives/how-to-use-the-git-protocol-through-a-http-connect-proxy/ > > Sure, I will try this tomorrow once in office. Thank you. I found a past relevant dicussion here [1]. Unfortunately, the socat method outlined in the above URL didn't work inside the office environment. Looks like the base requirement of port 9418 being open by proxy is not met. Its not a really hard to patch this locally and get the source repos using https. But ideally, if jhbuild could support multiple repo URLs (for fallback), this wouldn't repeat time and time again. [1] https://lists.webkit.org/pipermail/webkit-gtk/2013-October/001599.html Comment on attachment 235964 [details]
Patch
I think we are going to pass on this for the moment, given Philippe's comments about efficiency.
|