How to handle port merges on upgrade for pkg/portmaster/portupgrade/port... (was: Dealing with a port being merged into another)

Matthias Andree mandree at
Wed Nov 12 23:56:24 UTC 2014

Am 23.10.2014 um 12:01 schrieb Raphael Kubo da Costa:
> Hi everyone,
> One of the changes we (kde@) have made in the upcoming Qt 5.3.2 update
> is merging devel/qt5-qmldevtools into lang/qt5-qml.
> I'd now like to know what needs to be done to make it easy to everyone
> to upgrade their ports. By everyone I mean people using pkg as well as
> people using port{master,upgrade,whatnot}, and by "make it easy" I mean
> I don't want to have to write an UPDATING entry (that many people will
> not read) that tells people they need to manually remove qt5-qmldevtools
> from their systems before upgrading.
> Do I need CONFLICTS_INSTALL? Will everything be handled automatically?
> Is the UPDATING entry inevitable?

Greetings of the time of day,

So, here goes my belated reply...

portmaster will be happy with a MOVED entry and know about the
substitute port, in this situation it got tripped up by
<>, i. e.
/usr/local being preferred for linking over the local newly-built libs,
leading to failure during the link stage if the older version is
installed on the same system.

I've had too much trouble with portupgrade to bother with it for the
past five years or so.

We should be aware that poudriere or Tinderbox will *not* find such
upgrading problems for ports-based systems.

So I propose that we amend to the porter's handbook with a
recommendation to always test building an updated port revision on a
live system with the older (previous) port version installed.  Not just

Hope that helps.

Best regards,

More information about the freebsd-doc mailing list