path: root/meta/recipes-support/libproxy
diff options
authorInaky Perez-Gonzalez <>2012-03-01 09:44:34 +0000
committerRichard Purdie <>2012-03-01 16:09:00 +0000
commite579eb7f33462258c8e82a0936d970593614840d (patch)
treed5ab0d5cde731251eb76ad07d3ffba269d15889f /meta/recipes-support/libproxy
parentbdb341953ba7d8299cba4d49d857107fb7b01e5b (diff)
site.conf.sample: Fix broken SOCKS proxy setup and configuration
SOCKS proxy specification with git was using conflicting methods and thus was failing when mixed SOCKS needs were in place (requiring no proxy for some hosts and proxy for the rest) - GIT_PROXY_COMMAND is an environment variable GIT uses to OVERRIDE all proxy configuration in ~/.gitconfig or any other gitconfig. By using it to configure, it was breaking havoc on site git configuration or the one generated by bitbake in tmp/. Renamed to OE_GIT_PROXY_COMMAND in meta/conf/site.conf.sample (with a doc tidbit on the name chosen), meta/classes/base.bbclass. - The gitconfig generated by bitbake was wrong. There was a typo error (gitproxy vs gitProxy), thus all lines were being ignored. Fixed in meta/classes/base.bbclass. - The gitconfig generated was being placed in ${STAGING_DIR_NATIVE}/usr/etc/gitconfig; git was looking for it in ${STAGING_DIR_NATIVE}/etc/gitconfig. Fixed that in meta/classes/base.bbclass, at the same time creating a GIT_CONFIG_PATH variable, since it is also referenced in generate_git_config() and have all instances refer to that. Signed-off-by: Inaky Perez-Gonzalez <> Signed-off-by: Richard Purdie <>
Diffstat (limited to 'meta/recipes-support/libproxy')
0 files changed, 0 insertions, 0 deletions