Date: Mon, 15 Jan 2007 11:54:53 +0100 (CET) From: Matthias Buelow <mkb@incubus.de> To: FreeBSD-gnats-submit@FreeBSD.org Subject: ports/107948: pass fetch(1)-specific options to FETCH_CMD Message-ID: <20070115105453.1084735E77@luzifer.incubus.de> Resent-Message-ID: <200701151130.l0FBUJIA035793@freefall.freebsd.org>
next in thread | raw e-mail | index | archive | help
>Number: 107948 >Category: ports >Synopsis: pass fetch(1)-specific options to FETCH_CMD >Confidential: no >Severity: non-critical >Priority: medium >Responsible: freebsd-ports-bugs >State: open >Quarter: >Keywords: >Date-Required: >Class: change-request >Submitter-Id: current-users >Arrival-Date: Mon Jan 15 11:30:18 GMT 2007 >Closed-Date: >Last-Modified: >Originator: Matthias Buelow >Release: FreeBSD 5.5-STABLE i386 >Organization: Haters of Ports >Environment: System: FreeBSD none-of-your-business FreeBSD 5.5-STABLE #3: Tue Oct 31 06:51:02 CET 2006 ... i386 >Description: The fetch(1) command is using passive ftp by default, which doesn't seem to work with all ftp servers (for example, ftp.xemacs.org). The ports system is using an env variable FETCH_CMD to allow one to specify the command being used to fetch files (for example, wget --no-passive-ftp). However, in its inane design brokenness, ports passes fetch(1)- specific options to FETCH_CMD (-S ...), which makes the direct use of wget or ftp impossible. The mechanism should be fixed to allow for specifying other downloading commands. >How-To-Repeat: >Fix: A workaround is to use a small script as FETCH_CMD, which filters out unwanted options, like: wget ... $(echo $@|sed 's/-S *[0-9]*//') >Release-Note: >Audit-Trail: >Unformatted:
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20070115105453.1084735E77>