Upgrades that include netpbm

Barrie Stott zen146410 at zen.co.uk
Fri Jun 12 11:09:23 PDT 2015

On 12 Jun 2015, at 18:26, Mihai Moldovan wrote:

> On 12.06.2015 05:21 PM, Barrie Stott wrote:
>> Whenever I perform such an 'upgrade outdated', a message is displayed when trying to configure netpbm saying that I should force a deactivation of netpbm and then the upgrade stops. Normally I deactivate netpbm, upgrade netpbm and upgrade outdated.
>> Is there any reason why I cannot force deactivate netpbm before starting the 'upgrade aoutdated' in the first place?
> That would break other ports that depend upon netpbm. Worse, I think port will
> automatically re-activate it, if it comes to such a port.
> So you wouldn't win anything.
> Sadly, making netpbm conflict with itself at built time is the only way to make
> sure it doesn't use its own headers/libraries when compiling.
> Trace mode would fix that, but we currently have no way of activating or
> deactivating trace mode on a per-ports basis.
> Mihai

Many thanks for that, Mihai. groff and man are the only ports I use at present that depend on netpbm and I don't think that they would be involved in upgrading ports. Even so, since there are doubts, I'll continue doing upgrades as I do at present.


More information about the macports-users mailing list