port upgrade outdated order

[Chris Jones]

On 04/03/15 16:43, René J.V. Bertin wrote:
> On Wednesday March 04 2015 16:22:16 Chris Jones wrote:
>
>>> When a port fails to build because the project/package/whatever it provides doesn't support building with a previous version present, is that a port bug?
>>
>> As far as I am concerned its a bug in the port, or a bug in the upstream
>> project.
>
> I used to think like that, until I reported this kind of issue in one of Qt's component. It was not very delicately pointed out to me that it's common practice to build things without previous versions present (cf. the Debian and Ubuntu buildbots).
>
> So, no, it is apparently not considered a bug if something doesn't build when a previous version of it is installed in the destination. And given that, one can hardly expect port devs to "just fix this".

what upstream thinks doesn't change what I think, and that is all I was 
claiming, that *I* consider it either an upstream bug, or a port bug. We 
also don't have to agree on things ;)

If upstream cannot/wont fix, then if we want to keep the port in 
MacPorts, it should be worked around. trace mode (or anything that does 
the same thing, hides the installed version) strikes me as perfect here.

Chris