Skip site navigation (1)Skip section navigation (2)
Date:      Sun, 16 Feb 2025 19:02:28 +0000
From:      bugzilla-noreply@freebsd.org
To:        ports-bugs@FreeBSD.org
Subject:   [Bug 245495] www/qt5-webengine: build failure after devel/re2 upgrade
Message-ID:  <bug-245495-7788-uoSqbsL7YN@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-245495-7788@https.bugs.freebsd.org/bugzilla/>
References:  <bug-245495-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=3D245495

--- Comment #13 from John Hein <jcfyecrayz@liamekaens.com> ---
Created attachment 257589
  --> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=3D257589&action=
=3Dedit
[patch] experimental change to allow declaring build-time self-conflicts

(In reply to John Hein from comment #12)
Here's an experimental example that you can apply locally and see how well =
it
works.  What it does:

Allow declaring a build-time conflict with yourself if there are
known failures where it's hard to isolate the build to look for
source/object code in the working directories (instead of from
installed location of the port).

Instead of setting CONFLICTS*, however, the strong preference is to make the
build of a particular port be able to isolate itself regardless of what is
installed (e.g., ensuring that linking and compiling  operations point to l=
ibs
and include files in the port being built rather than the installed files o=
f a
currently installed version of that port).  But in cases where it's difficu=
lt
to do that for a particular port, then setting CONFLICTS_BUILD might be a g=
ood
choice to avoid running a long build that is known to eventually fail when a
version of itself is already installed.

I'm not necessarily advocating this patch yet.  I would like to understand =
if
there may be a good reason for the self-check exclusion for CONFLICTS_BUILD=
S.

--=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-245495-7788-uoSqbsL7YN>