Bug 89363 - [patch] fetchindex does not respect FETCH_ENV from /etc/make.conf
Summary: [patch] fetchindex does not respect FETCH_ENV from /etc/make.conf
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: Normal Affects Only Me
Assignee: Port Management Team
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-11-21 12:20 UTC by Sergey Matveychuk
Modified: 2006-01-12 04:18 UTC (History)
0 users

See Also:

Attachments
fetchindex.patch (734 bytes, patch)
2005-11-21 12:20 UTC, Sergey Matveychuk 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Sergey Matveychuk freebsd_committer freebsd_triage 2005-11-21 12:20:17 UTC 
	
	Users, who set FETCH_ENV=http://proxy in /etc/make.conf
	has found 'make fetchindex' ignores their proxy.

How-To-Repeat: 	
	Behind a firewall, put FETCH_ENV=http://your-proxy:port 
	into /etc/make.conf, go to ports dir and execute:
	make fetchindex

	The patch makes fetchindex behaviour more consistent.
Comment 1 Sergey Matveychuk freebsd_committer freebsd_triage 2005-11-21 12:21:04 UTC 
Responsible Changed
From-To: freebsd-ports-bugs->portmgr

Over to maintainer
Comment 2 Sergey Matveychuk freebsd_committer freebsd_triage 2005-11-21 12:29:28 UTC 
Just after I've submitted the PR I've found mnag's ports/89201.

Only difference between them is: mnag does not use env(1).
So, let's portmgr decide which one should be committed.
-- 
Sem.
Comment 3 Mark Linimon freebsd_committer freebsd_triage 2006-01-12 04:18:09 UTC 
State Changed
From-To: open->closed

Please see the combined patch in ports/89809 which attempts to fix 
multiple problems in this area.