Am 02.08.2012 11:20, schrieb Oon-Ee Ng:
> On my personal machine I've long-since changed XferCommand, but on
> doing a new install on another machine with the latest iso (behind a
> proxy, which is a first for me), I figured out that a problem I was
> having was linked to pacman NOT using wget by default. Is it just me,
> or wasn't wget the default before?

As Mantas correctly indicated, pacman does not use an external download
manager by default, but it downloads files internally using curl.

Why would you even change that behaviour? Using an external download
manager only slows pacman down.

> Just to be clear, I was getting proxy related errors even after
> changing /etc/wgetrc (as instructed in the beginner's guide).

It's a wiki. Everyone can edit it, so everyone's misconceptions are in
there.

> > On my personal machine I've long-since changed XferCommand, but on
> > doing a new install on another machine with the latest iso (behind a
> > proxy, which is a first for me), I figured out that a problem I was
> > having was linked to pacman NOT using wget by default. Is it just me,
> > or wasn't wget the default before?
>
> As Mantas correctly indicated, pacman does not use an external download
> manager by default, but it downloads files internally using curl.
>
> Why would you even change that behaviour? Using an external download
> manager only slows pacman down.

Considering the bugs that wget has had without -o that could be
dangerous as root as well as other bugs in curl. I've always thought
system updates should be downloading as say a _pacman user. One day I
may get enough free time to sort that out.


--
__________________________________________________ _____________________

'Write programs that do one thing and do it well. Write programs to work
together. Write programs to handle text streams, because that is a
universal interface'

(Doug McIlroy)
__________________________________________________ _____________________

On Thu, Aug 2, 2012 at 4:29 AM, Mantas MikulÄ—nas <grawity@gmail.com> wrote:

> libcurl honors $http_proxy in environment (lowercase – not $HTTP_PROXY).


Probably the problem comes with the use of sudo. In my case at work I use
/etc/profile.d/ to get around the proxy, and configure sudo to preserve the
proxy variables inherited from the file in /etc/profile.d/

On Thu, Aug 2, 2012 at 5:42 PM, Thomas Bächler <thomas@archlinux.org> wrote:
> Am 02.08.2012 11:20, schrieb Oon-Ee Ng:
>> On my personal machine I've long-since changed XferCommand, but on
>> doing a new install on another machine with the latest iso (behind a
>> proxy, which is a first for me), I figured out that a problem I was
>> having was linked to pacman NOT using wget by default. Is it just me,
>> or wasn't wget the default before?
>
> As Mantas correctly indicated, pacman does not use an external download
> manager by default, but it downloads files internally using curl.
>
> Why would you even change that behaviour? Using an external download
> manager only slows pacman down.

In my personal laptop's case - I use aria2c due to horrible network
communicativity (is that a word?) in various locations I regularly
visit.
>
>> Just to be clear, I was getting proxy related errors even after
>> changing /etc/wgetrc (as instructed in the beginner's guide).
>
> It's a wiki. Everyone can edit it, so everyone's misconceptions are in
> there.
>
And I've edited it to correct it, thank you all for your clarifications.

On Thu, Aug 2, 2012 at 10:38 PM, German Cabarcas <cmdr.chili@gmail.com> wrote:
> On Thu, Aug 2, 2012 at 4:29 AM, Mantas MikulÄ—nas <grawity@gmail.com> wrote:
>
>> libcurl honors $http_proxy in environment (lowercase – not $HTTP_PROXY).
>
>
> Probably the problem comes with the use of sudo. In my case at work I use
> /etc/profile.d/ to get around the proxy, and configure sudo to preserve the
> proxy variables inherited from the file in /etc/profile.d/

In this specific case (new install behind a proxy) sudo doesn't yet
come into the picture as we're still running as root at that point.