port upgrade outdated order

[Mihai Moldovan]

On 04.03.2015 02:11 AM, René J.V. Bertin wrote:
> On Tuesday March 03 2015 19:00:16 Lawrence Velázquez wrote:
>
>>>> note that trace mode fixes this ;-)
>>> How so?
>> By masking files that aren't part of the operating system, Xcode, or port dependencies.
> Hmmm, can't say the term "trace" evokes that for me :)
>
> I think I understood that ports can opt out from this mode, no?

Trace mode is (so far) enabled iff passing the -t flag to port.


>  Can they also activate it?

Sadly, no. Not yet. If that was possible, we could sort out quite some
conflicting builds automatically (like packages picking up currently
installed libraries when building or using stuff in ${prefix}/include
when they really "mean" to use the new version headers in their
worksrcpath.)

The conflicts_build PortGroup would certainly benefit from that.



Mihai

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 884 bytes
Desc: OpenPGP digital signature
URL: <https://lists.macosforge.org/pipermail/macports-dev/attachments/20150304/829c9dcc/attachment.sig>