On Thu, 10 Aug 2006, Augusto Arcoverde da Rocha wrote:
[...]
Yes, it's supported but isn't a standart and has no guaranties to
exists on all architectures as Alexander said in a reply in this list
$http_proxy and $ftp_proxy may not be very well documented but they are
defacto standards and as
On 8/11/06, Francois Gouget [EMAIL PROTECTED] wrote:
On Thu, 10 Aug 2006, Augusto Arcoverde da Rocha wrote:
[...]
Yes, it's supported but isn't a standart and has no guaranties to
exists on all architectures as Alexander said in a reply in this list
$http_proxy and $ftp_proxy may not be very
On Fri, 11 Aug 2006, Augusto Arcoverde da Rocha wrote:
[...]
But, I have read in somewhere a reply from Alexander about avoiding
environment variables. However, I can't find this message again.
Maybe you are thinking about the one in which he argues against
introducing new obsucure
On Thu, 3 Aug 2006, Augusto Arcoverde da Rocha wrote:
Exists a opened bug report about the problem which this patch is suposed to
fix:
http://bugs.winehq.org/show_bug.cgi?id=5625
Can someone give some comments for what this pach wasn't applied?
As far as I can see the patch seems to assume
On Thu, 2006-08-10 at 13:33 +0200, Francois Gouget wrote:
There may also be a way to specify a password ('[EMAIL PROTECTED]'?).
Format is:
[user[:[EMAIL PROTECTED]:port]
--
Dimi Paun [EMAIL PROTECTED]
Lattica, Inc.
Hu...
Then a better approach would be avoid environment variables, as this
seems to be a Wine development directive, and use the right format for
the proxy configuration string.
Can someone point more questions about Wine proxy configuration which
could improve that patch?
Regards,
Augusto
Hi,
Dimi Paun wrote:
On Thu, 2006-08-10 at 13:33 +0200, Francois Gouget wrote:
There may also be a way to specify a password ('[EMAIL PROTECTED]'?).
Format is:
[user[:[EMAIL PROTECTED]:port]
If I google for http_proxy, I always find this additionally prefixed by
http://;. Some have
Hi,
Augusto Arcoverde da Rocha wrote:
Hu...
Then a better approach would be avoid environment variables, as this
seems to be a Wine development directive, and use the right format for
the proxy configuration string.
I disagree. I think it makes sense to support general environment
On 8/10/06, Tobias Burnus [EMAIL PROTECTED] wrote:
Hi,
Augusto Arcoverde da Rocha wrote:
Hu...
Then a better approach would be avoid environment variables, as this
seems to be a Wine development directive, and use the right format for
the proxy configuration string.
I disagree. I
Hi,
Augusto Arcoverde da Rocha schrieb:
IMHO, the current password exposition is a ugly thing:
$ export http_proxy=http://user:__**password**[EMAIL PROTECTED]:8080
I wouldn't worry to much about a PROXY password. I mean who can access
files and environment variables? Basically only you and the
Exists a opened bug report about the problem which this patch is suposed to fix:
http://bugs.winehq.org/show_bug.cgi?id=5625
Can someone give some comments for what this pach wasn't applied?
Thanks,
Augusto Arcoverde da Rocha
11 matches
Mail list logo