Date: Thu, 08 Jul 2021 23:04:20 +0000 From: bugzilla-noreply@freebsd.org To: ports-bugs@FreeBSD.org Subject: [Bug 257063] archivers/star: Do not install 'gnutar' for it is broken Message-ID: <bug-257063-7788-ISCdoqvQRS@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-257063-7788@https.bugs.freebsd.org/bugzilla/> References: <bug-257063-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=3D257063 Robert Clausecker <fuz@fuz.su> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|maintainer-feedback?(fuz@fu |maintainer-feedback+ |z.su) | CC| |gecko@FreeBSD.org --- Comment #1 from Robert Clausecker <fuz@fuz.su> --- (In reply to ice from comment #0) Hi, It is unfortunate that Firefox-esr wrongly detects star's gnutar binary as a GNU tar. This seems to be an error in the way the port is set up: archivers/gtar is not given as a build dependency and yet the port looks fo= r a GNU tar binary. Why is that so? Adding the maintainer of the www/firefox-= esr port to CC. I would like to continue providing a gnutar binary if possible as that bina= ry is part of the star distribution and its name does not collide with any oth= er command I am aware of (FreeBSD ports install GNU tar as gtar not gnutar, so there is no collision here). If a port wrongly picks this program over /usr/bin/tar or gtar, the port needs to be patched to always pick the corre= ct tar program. I mean we don't let ports pick random gcc binaries over ${CC} either... If there is no other remedy to the issue, I can however go ahead and set up= an option to make installing the gnutar binary conditional. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-257063-7788-ISCdoqvQRS>