On Thu, Nov 01, 2018 at 08:54:16AM +0100, Stefan Esser wrote: > Am 01.11.18 um 03:38 schrieb Jonathan Chen: > > On Thu, 1 Nov 2018 at 15:35, Montgomery-Smith, Stephen > > <[email protected]> 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
You can already set CONFLICT_BUILD= firefox-62.* -- Mathieu Arnold
signature.asc
Description: PGP signature
