Date: Thu, 09 Feb 2023 22:08:25 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 269432] ports: FETCH_ARGS / FETCH_CMD can't accept a string with spaces Message-ID: <bug-269432-7788-sqcj1KuPl4@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-269432-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-269432-7788@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D269432 Tatsuki Makino <tatsuki_makino@hotmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |tatsuki_makino@hotmail.com --- Comment #5 from Tatsuki Makino <tatsuki_makino@hotmail.com> --- I too thought it would be better to use curl for Bug 260699 issue. As a result, the following variable definitions are considered necessary. FETCH_DEPENDS+=3D ${LOCALBASE}/bin/curl:ftp/curl DISABLE_SIZE=3D yes FETCH_CMD=3D ${CURL_BINARY} ${CURL_ARGS} FETCH_ENV=3D CURL_BINARY?=3D ${LOCALBASE}/bin/curl CURL_ARGS?=3D\ --continue-at - \ --ftp-pasv \ --location \ --no-clobber \ --remote-name \ --remote-time These should make the behavior equivalent to fetch. Since the do-fetch target command has been changed to run Mk/Scripts/do-fetch.sh, some command arguments can no longer be passed. One of these is the -o option, but it may not be possible to replace it with curl as is because fetch and curl behave slightly differently. This was a bit of a derailment, but I wrote it because I thought we were all going to the same destination of purpose :) --=20 You are receiving this mail because: You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-269432-7788-sqcj1KuPl4>