Date: Fri, 27 Jan 2006 13:16:31 -0500 (EST) From: Stuart Barkley <stuartb@4gh.net> To: Andrey Slusar <anray@FreeBSD.org> Cc: freebsd-ports-bugs@FreeBSD.org Subject: Re: ports/92226: Make sure Opera finds FreeBSD 4 compat libraries Message-ID: <20060127130615.F20072@freeman.4gh.net> In-Reply-To: <200601271102.k0RB2JkZ005026@freefall.freebsd.org> References: <200601271102.k0RB2JkZ005026@freefall.freebsd.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 27 Jan 2006 at 11:02 -0000, Andrey Slusar wrote: > Synopsis: Make sure Opera finds FreeBSD 4 compat libraries > > Responsible-Changed-From-To: freebsd-ports-bugs->anray > Responsible-Changed-By: anray > Responsible-Changed-When: Fri Jan 27 11:02:19 UTC 2006 > Responsible-Changed-Why: > I'll take it. > > http://www.freebsd.org/cgi/query-pr.cgi?pr=92226 This patch has been applied today. This seems like a pragmatic but very broken way to deal with the problem. If the user has the compat4x package installed but not enabled then other packages should not be grovelling into compat4x. More appropriate solutions would seem to be: - Fix the compat4x package to default to enabling the compatibility libraries. The compat4x and compat5x packages are currently broken anyway. They generate confusing warnings on system boot since they don't have an explicit default of enable=YES or enable=NO. There may be other issues with why compat4x and compat5x don't default to enabled but this seems a reasonable default. The enable knob is important to have and I do like that many packages default to not enabled but for libraries defaulting to disabled seems not necessary. - Put a note in pkg-message that enable_compat4x="YES" is required. - Put code in the install script which warns if the required libraries are not found.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20060127130615.F20072>