Date: Tue, 15 Nov 2022 07:52:36 +0100 From: Alex Dupre <ale@FreeBSD.org> To: Jamie Landeg-Jones <jamie@catflap.org>, freebsd-ports@freebsd.org, freebsd-users@freebsd.org Cc: jailbird@fdf.net Subject: Re: Intentionally bad port behaviour Message-ID: <d60200b2-ad4c-ee82-5eaa-e07b26670f34@FreeBSD.org> In-Reply-To: <202211150005.2AF05WDv063547@donotpassgo.dyslexicfish.net> References: <202211150005.2AF05WDv063547@donotpassgo.dyslexicfish.net>
next in thread | previous in thread | raw e-mail | index | archive | help
Jamie Landeg-Jones wrote: > What's the policy on dodgy acting ports? >=20 > I had elinks crash (well, the spidermonkey part crashed) >=20 > elinks then accused me of editting the config file manually (I hadn't) > and then went into an intentional endless loop. >=20 > I think this should be patched out: I think there are (at least) two issues in the port: 1) that code should not be compiled in, because it's in the "else" branch of a "#ifdef HAVE_EXECINFO_H", so something is broken in the port/configure script 2) the port has a "CONIGURE_ENV" line, that is quite surely a typo --=20 Alex Dupre
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?d60200b2-ad4c-ee82-5eaa-e07b26670f34>