FreeBSD Port: firefox-63.0.1,1 multiple errors build

Stefan Esser se at freebsd.org
Thu Nov 1 07:54:22 UTC 2018


Am 01.11.18 um 03:38 schrieb Jonathan Chen:
> On Thu, 1 Nov 2018 at 15:35, Montgomery-Smith, Stephen
> <stephen at missouri.edu> wrote:
> [...]
>> I only started using portupgrade recently.  I find it rather unreliable.
>>  I think the problem is that some ports need to be deleted before they
>> can be built successfully.
> 
> For reliable port builds, you need use port builders that use clean
> environments; ie poudriere or synth

True, but we used to make ports build with a previous version installed,
whenever possible. The problems are generally caused by the build process
picking up include files or libraries from LOCALBASE instead of from the
port's source directory.

I'd expect a port maintainer to check for easy fixes to such build problems.

Maybe we should add a port variable that is true if a port conflicts with
earlier versions of itself. That would indicate to port build tools like
portmaster or portupgrade that the old version should be deleted before
starting the build of the new version (and to re-install the old version
if the build of the new one fails).

E.g.:

CONFLICTS_WITH_ITSELF=	yes

I'd be willing to integrate support for such a functionality into portmaster,
if it was accepted in the ports framework.

Regards, STefan

PS: And yes, there are good reasons to keep support for tools that are
    lighter-weight than poudriere and more portable than synth in the
    ports system.


More information about the freebsd-ports mailing list