All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rainer Koenig <Rainer.Koenig@ts.fujitsu.com>
To: Openembedded Core <openembedded-core@lists.openembedded.org>
Subject: OE core behind a company firewall
Date: Tue, 25 Oct 2011 10:44:08 +0200	[thread overview]
Message-ID: <4EA676D8.30206@ts.fujitsu.com> (raw)

Hi,

I just tried out OE core according to the instructions at

http://www.angstrom-distribution.org/building-angstrom and

http://git.angstrom-distribution.org/cgi-bin/cgit.cgi/meta-texasinstruments/tree/README

At home this works fine, but being inside my company's firewall during
the day I have some comments on the oebb.sh script.

First I didn't get that corkscrew stuff for git working. Don't know
whats wrong but since I had a working git-proxy setting for my SOCKS
server I modified the script so that it works for me.

###############################################################################
# CONFIG_GIT_PROXY() - Configure GIT proxy information
###############################################################################
function config_git_proxy()
{
    if [ ! -f ${GIT_CONFIG_DIR}/git-proxy.sh ]
    then
        mkdir -p ${GIT_CONFIG_DIR}
       cat > ${GIT_CONFIG_DIR}/git-proxy.sh <<_EOF
#!/bin/sh
/usr/bin/env /usr/bin/connect -S ${PROXYHOST}:1080 \$*
_EOF
        chmod +x ${GIT_CONFIG_DIR}/git-proxy.sh
        export GIT_PROXY_COMMAND=${GIT_CONFIG_DIR}/git-proxy.sh
    fi
}

Luckily http_proxy and SOCKS share the same server, so I could use
${PROXYHOST} here. :-)

With this setup I got oebb.sh working for me. But then I ran into
problems with building gcc-core-initial and I first thought its because
the SRC_URI is "svn://" but that was a wrong guess. Problem was that the
download was interrupted somehow and so unpacking the tgz failed.

Anyway, thinking of svn:-URIs I wonder about what will happen when
I need to access a SVN repo with the svn protocol. SVN seems to be a
pain in the ass when trying to use a SOCKS server. Well, actually there
is no need, because its just 3 recipes that I found which will use the
svn-protocol and its not likely that I need them for my project.

$ find -name "*.bb" | xargs grep "svn://" | grep -v proto
./sources/openembedded-core/meta/recipes-sato/puzzles/puzzles_r9306.bb:#SRC_URI
= "svn://ixion.tartarus.org/main;module=puzzles;rev=${MOD_PV}"
./sources/meta-smartphone/meta-shr/recipes-shr/3rdparty/openmoko-gps_svn.bb:SRC_URI
= "svn://forge.bearstech.com/forge/openmoko;module=gps"
./sources/meta-smartphone/meta-shr/recipes-shr/3rdparty/om-neon_svn.bb:SRC_URI
= "svn://svn.projects.openmoko.org/svnroot/neon;module=trunk"
./sources/meta-smartphone/meta-shr/recipes-shr/3rdparty/spojegui_svn.bb:SRC_URI
= "svn://xeres.cz/spoje/trunk;module=build"

Regards
Rainer
-- 
Dipl.-Inf. (FH) Rainer Koenig
Project Manager Linux Clients
Dept. PDG WPS R&D SW OSE

Fujitsu Technology Solutions
Bürgermeister-Ullrich-Str. 100
86199 Augsburg
Germany

Telephone: +49-821-804-3321
Telefax:   +49-821-804-2131
Mail:      mailto:Rainer.Koenig@ts.fujitsu.com

Internet         ts.fujtsu.com
Company Details  ts.fujitsu.com/imprint.html



                 reply	other threads:[~2011-10-25  8:51 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4EA676D8.30206@ts.fujitsu.com \
    --to=rainer.koenig@ts.fujitsu.com \
    --cc=openembedded-core@lists.openembedded.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.