Date: Fri, 28 Apr 2017 18:36:12 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-ports-bugs@FreeBSD.org Subject: [Bug 218827] r438058 and r438901 cause trouble for PACKAGES settings with colons in them Message-ID: <bug-218827-13-EcA2fcXl1W@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-218827-13@https.bugs.freebsd.org/bugzilla/> References: <bug-218827-13@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=3D218827 Dimitry Andric <dim@FreeBSD.org> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|--- |Not A Bug Status|New |Closed --- Comment #7 from Dimitry Andric <dim@FreeBSD.org> --- (In reply to Baptiste Daroussin from comment #6) > I think surrounding the target with quotes should be enough, but I can't = try > it Did you mean in bsd.port.mk, or in make.conf? But indeed, quoting the vale= of PACKAGES, or escaping the colons, in /etc/make.conf makes it work again. E.g.: PACKAGES?=3D"/share/dim/dist/FreeBSD:12:i386/latest" or: PACKAGES?=3D/share/dim/dist/FreeBSD\:12\:i386/latest both allow me to build ports, even with r438058 and r438901 applied. Let's close this bug then, but maybe it would be nice to have some sort of warning in bsd.port.mk about using colons (or other make metacharacters) in ports-related make.conf variables? --=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-218827-13-EcA2fcXl1W>