what about something like
ifeq (,$(findstring get-orig-source, $(MAKECMDGOALS)))
export http_proxy=http://127.0.0.1:9/
endif
so unless called with get-orig-source -- it would get defined... ?
On Wed, 06 Feb 2013, Piotr Ożarowski wrote:
> [Dmitrijs Ledkovs, 2013-02-06]
> > On 5 February 2013 17
On Feb 06, 2013, at 11:18 AM, Dmitrijs Ledkovs wrote:
>I should add a hook to export that for the build & binary stages of the
>package build in my sbuild config (but not the fetching build-deps) Also one
>should be able to set that in debuild hooks.
That would help make local sbuilds act more li
On Feb 06, 2013, at 01:13 PM, Piotr Ożarowski wrote:
>FTR: pybuild does that by default (http_proxy=http://127.0.0.1:9/)
Nice.
>it probably should be changed to not overwrite existing http_proxy (if set)
>or to make it possible to disable it.
The only case where I found I had to unset http_prox
[Dmitrijs Ledkovs, 2013-02-06]
> On 5 February 2013 17:48, Barry Warsaw wrote:
> > http://mail.python.org/pipermail/catalog-sig/2013-February/004831.html
>
> I should add a hook to export that for the build & binary stages of
FTR: pybuild does that by default (http_proxy=http://127.0.0.1:9/)
it
On 5 February 2013 17:48, Barry Warsaw wrote:
> There's been a lot of discussion lately on various forums (e.g. catalog-sig)
> about PyPI security. I realized that our recommendation for setting
> http_proxy in debian/rules can have beneficial local security implications.
>
&g
There's been a lot of discussion lately on various forums (e.g. catalog-sig)
about PyPI security. I realized that our recommendation for setting
http_proxy in debian/rules can have beneficial local security implications.
More details here:
http://mail.python.org/pipermail/catalog-sig
6 matches
Mail list logo
