Skip to contentSkip to conversation

eglibc: use HTTP for svn checkout

PATCH In review Ryan D Phillips 7 participants 11 messages Dec 13, 2010 – Dec 15, 2010

lore
Share & tools
lore
#0 lore raw

PATCH 1/1 eglibc: use HTTP for svn checkout

SVN over HTTP is a more reliable transport for developers behind
restrictive
proxies.

Regards,
Ryan

From c0a5ad76e64d961735b5c07326d86107ef98f6a1 Mon Sep 17 00:00:00 2001
From: Ryan D Phillips <[email protected]>
Date: Mon, 13 Dec 2010 10:00:27 -0600
Subject: [PATCH] eglibc: Use HTTP for svn checkout

SVN over HTTP is a more reliable transport for developers behind restrictive proxies.

---
 recipes/eglibc/eglibc_2.10.bb |    2 +-
 recipes/eglibc/eglibc_2.11.bb |    2 +-
 recipes/eglibc/eglibc_2.12.bb |    2 +-
 recipes/eglibc/eglibc_2.9.bb  |    2 +-
 4 files changed, 4 insertions(+), 4 deletions(-)
recipes/eglibc/eglibc_2.10.bb +1 -1
index 1eab7eb..e873bea 100644
@@ -7,7 +7,7 @@ PR = "${INC_PR}.10"
 PR_append = "+svnr${SRCPV}"
 SRCREV="10152"
 EGLIBC_BRANCH="eglibc-2_10"
-SRC_URI = "svn://svn.eglibc.org/branches;module=${EGLIBC_BRANCH};proto=svn \
+SRC_URI = "svn://svn.eglibc.org/svn/branches;module=${EGLIBC_BRANCH};proto=http \
            file://eglibc-svn-arm-lowlevellock-include-tls.patch \
            file://armv4t-interworking.patch \
            file://IO-acquire-lock-fix.patch \
recipes/eglibc/eglibc_2.11.bb +1 -1
index b249f29..4a6f25d 100644
@@ -8,7 +8,7 @@ PR = "${INC_PR}.8"
 PR_append = "+svnr${SRCPV}"
 SRCREV="12231"
 EGLIBC_BRANCH="eglibc-2_11"
-SRC_URI = "svn://svn.eglibc.org/branches;module=${EGLIBC_BRANCH};proto=svn \
+SRC_URI = "svn://svn.eglibc.org/svn/branches;module=${EGLIBC_BRANCH};proto=http \
            file://eglibc-svn-arm-lowlevellock-include-tls.patch \
            file://IO-acquire-lock-fix.patch \
            file://shorten-build-commands.patch \
recipes/eglibc/eglibc_2.12.bb +1 -1
index 1285568..214da69 100644
@@ -8,7 +8,7 @@ PR = "${INC_PR}.7"
 PR_append = "+svnr${SRCPV}"
 SRCREV="12230"
 EGLIBC_BRANCH="eglibc-2_12"
-SRC_URI = "svn://svn.eglibc.org/branches;module=${EGLIBC_BRANCH};proto=svn \
+SRC_URI = "svn://svn.eglibc.org/svn/branches;module=${EGLIBC_BRANCH};proto=http \
            file://eglibc-svn-arm-lowlevellock-include-tls.patch \
            file://IO-acquire-lock-fix.patch \
            file://shorten-build-commands.patch \
recipes/eglibc/eglibc_2.9.bb +1 -1
index c06345e..b096469 100644
@@ -7,7 +7,7 @@ PR = "${INC_PR}.10"
 PR_append = "+svnr${SRCPV}"
 SRCREV="10153"
 EGLIBC_BRANCH="eglibc-2_9"
-SRC_URI = "svn://svn.eglibc.org/branches;module=${EGLIBC_BRANCH};proto=svn \
+SRC_URI = "svn://svn.eglibc.org/svn/branches;module=${EGLIBC_BRANCH};proto=http \
            file://eglibc-svn-arm-lowlevellock-include-tls.patch \
            file://armv4t-interworking.patch \
            file://IO-acquire-lock-fix.patch \
Signature · 1 line
1.7.2.3
#2 lore raw
Quoted 9 lines · Khem Raj
Quoted 4 lines · Ryan D Phillips

SVN over HTTP is a more reliable transport for developers behind
restrictive
proxies.

and how much slower/faster is it when compared to svn protocol ?

The speed depends on which subversion client backend someone is using. HTTP will be slower than using the svn native protocol, but the serf subversion backend will perform parallel fetches.

I would like to see this patch get into the OE tree to make the tree more robust to proxies. Currently, this is the only customization I need for the projects I work on.

Regards,
Ryan Phillips

#3 lore raw
Quoted 11 lines · Ryan D Phillips
Quoted 9 lines · Khem Raj
Quoted 4 lines · Ryan D Phillips

SVN over HTTP is a more reliable transport for developers behind restrictive
proxies.

and how much slower/faster is it when compared to svn protocol ?

Quoted 7 lines

The speed depends on which subversion client backend someone is using. HTTP will be slower than using the svn native protocol, but the serf subversion backend will perform parallel fetches.

I would like to see this patch get into the OE tree to make the tree more robust to proxies. Currently, this is the only customization I need for the projects I work on.

Note that if you use a mirror site with the SVN checkout archive in it, you won't try and do the fetch at all. This may or may not be applicable to your case. For your case I think what we really want is a way to globally toggle the svn protocol argument.

Signature · 2 lines
Tom Rini
Mentor Graphics Corporation
#4 lore raw
Quoted 19 lines · Tom Rini
Quoted 18 lines · Ryan D Phillips
Quoted 11 lines · Khem Raj
Quoted 5 lines · Ryan D Phillips

SVN over HTTP is a more reliable transport for developers behind restrictive
proxies.

and how much slower/faster is it when compared to svn protocol ?

The speed depends on which subversion client backend someone is using. HTTP will be slower than using the svn native protocol, but the serf subversion backend will perform parallel fetches.

Quoted 8 lines
Quoted 3 lines

I would like to see this patch get into the OE tree to make the tree more robust to proxies. Currently, this is the only customization I need for the projects I work on.

Note that if you use a mirror site with the SVN checkout archive in it, you won't try and do the fetch at all.  This may or may not be applicable to your case.  For your case I think what we really want is a way to globally toggle the svn protocol argument.

yes that would be something more useful. I guess we could add it to all SCM fetching recipes.

Quoted 10 lines

--
Tom Rini
Mentor Graphics Corporation

_______________________________________________
Openembedded-devel mailing list
[email protected]
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-devel

#5 lore raw
Quoted 7 lines · Khem Raj
Quoted 4 lines

Note that if you use a mirror site with the SVN checkout archive in it, you won't try and do the fetch at all.  This may or may not be applicable to your case.  For your case I think what we really want is a way to globally toggle the svn protocol argument.

yes that would be something more useful. I guess we could add it to all SCM fetching recipes.

I wonder if the PREMIRRORS/MIRRORS handling is smart enough to let us use its regex for the components to replace protocol= in the url parameters.

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#6 lore raw
Quoted 6 lines · Chris Larson
Quoted 5 lines · Khem Raj
Quoted 4 lines

Note that if you use a mirror site with the SVN checkout archive in it, you won't try and do the fetch at all. This may or may not be applicable to your case. For your case I think what we really want is a way to globally toggle the svn protocol argument.

Quoted 6 lines
Quoted 2 lines

yes that would be something more useful. I guess we could add it to all SCM fetching recipes.

I wonder if the PREMIRRORS/MIRRORS handling is smart enough to let us use its regex for the components to replace protocol= in the url parameters.

This won't suffice, because svn may have different URLs for svn and http, like in the discussed patch (branches vs. svn/branches):

-SRC_URI = "svn://svn.eglibc.org/branches;module=${EGLIBC_BRANCH};proto=svn \
+SRC_URI = "svn://svn.eglibc.org/svn/branches;module=${EGLIBC_BRANCH};proto=http \

Regards,
Andreas

#7 lore raw
Quoted 17 lines · Andreas Oberritter
Quoted 6 lines · Chris Larson
Quoted 5 lines · Khem Raj
Quoted 4 lines

Note that if you use a mirror site with the SVN checkout archive in it, you won't try and do the fetch at all.  This may or may not be applicable to your case.  For your case I think what we really want is a way to globally toggle the svn protocol argument.

Quoted 6 lines
Quoted 2 lines

yes that would be something more useful. I guess we could add it to all SCM fetching recipes.

I wonder if the PREMIRRORS/MIRRORS handling is smart enough to let us use its regex for the components to replace protocol= in the url parameters.

This won't suffice, because svn may have different URLs for svn and http, like in the discussed patch (branches vs. svn/branches):

Quoted 8 lines

-SRC_URI = "svn://svn.eglibc.org/branches;module=${EGLIBC_BRANCH};proto=svn

\
+SRC_URI = "svn://svn.eglibc.org/svn/branches;module=${EGLIBC_BRANCH};proto=http

\

And of course, changes to the url can also be done via PREMIRRORS. You'd just have the first one a specific entry to redirect eglibc, and the second a fallback for non-specific. Of course, there's nothing wrong with using bbappend/amend.inc for this, just another possibility.

Signature · 5 lines
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
#8 lore raw
In reply to Ryan D Phillips
Quoted 13 lines · Ryan D Phillips
Quoted 11 lines · Khem Raj
Quoted 5 lines · Ryan D Phillips

 SVN over HTTP is a more reliable transport for developers behind restrictive
proxies.

and how much slower/faster is it when compared to svn protocol ?

Quoted 7 lines

The speed depends on which subversion client backend someone is using. HTTP will be slower than using the svn native protocol, but the serf subversion backend will perform parallel fetches.

I would like to see this patch get into the OE tree to make the tree more robust to proxies. Currently, this is the only customization I need for the projects I work on.

Yes your pie :) but this is not the only problem I guess in OE with regard to fetching behind the proxies.
you can also use a appending mechanism in your layer and make this change without changing OE at all

Quoted 4 lines

Regards,
Ryan Phillips

#9 lore raw
In reply to Ryan D Phillips
Quoted 3 lines · Ryan D Phillips

I would like to see this patch get into the OE tree to make the tree more robust to proxies. Currently, this is the only customization I need for the projects I work on.

fwiw, I wrote a local patch for bitbake

          https://www.cvg.de/people/ensc/0004-svn-tunnel.patch

which allows fetching of svn:// uris through an http proxy (which must be configured to allow CONNECTs to svn servers). I thought it would be some local hack but when there is wider interest I will submit it to the bitbake ml.

Enrico