About adding a version component: the case of Infinality (was depends_run should ignore +/- universal?!)

Ryan Schmidt ryandesign at macports.org
Mon Jan 26 02:57:10 PST 2015

On Jan 23, 2015, at 4:56 AM, René J.V. Bertin wrote:

> Working on cairo yesterday I did notice something weird though that didn't seem to be due to any changes I made. As soon as I bumped the cairo version from 1.12.16 to 1.14.0, I started getting errors on how I was requesting a different set of variants when doing `port patch`, `port configure` and `port destroot`. I wasn't, and often the set of original variants shown didn't correspond to those I had installed nor to those I had been asking for, and the errors persisted after a port clean or a change to the portfile that caused an automatic port clean.
> I also saw error messages about failures to upgrade freetype and/or fontconfig at the end of the log output, while those ports were up to date, and port -y didn't show them among the ports to be upgraded.
> I finally noticed that adding -n to the port options allowed me to continue without all those errors, and they stopped after I installed a satisfying new cairo build.
> It felt like a circular dependency, but thinking about it, I realise that cairo is a dependency for many of the ports I have installed. It's just the first time I notice something like this, is it expectable behaviour?

I've never heard of any of these problems. They sound like the kind of issues that cleaning the port would solve, but you said it doesn't, so I don't know what else to tell you.

More information about the macports-dev mailing list