On Aug 22, 2012, at 7:20 AM, Michael Dickens wrote:
> Hmm … does (I think it's called) rev-update do its thing after installing
> from archive? It's the post-install "Updating database of binaries" and
> "Scanning binaries for linking errors" check. If it does, then it should
> catch the linking error between qt4-mac +framework and gnuplot, though I'm
> not sure what it can do if an older version of gnuplot was installed from
> archive that is not compatible with the current qt4-mac install. The
> archival capabilities can only go so far in terms of variants.
>
> I have thought about qt4-mac's dual library / framework build, since it
> causes these sorts of issues. I'm wondering if trying to install qt4-mac as
> dual framework / library would work: install as framework internally (to the
> Qt build), and then link from the frameworks into ${prefix}/include/Qt* and
> ${prefix}/lib/libQt*. The former is already done, and seems to work well.
> Doing the latter is a relatively simple extension of the former. If both
> libraries and frameworks were installed, always, then dependent ports could
> choose which one to link to and would, after the change, always be backwards
> compatible with older versions. Yes, this might make sense to look into.
>
> Thoughts on the above? - MLDWould frameworks work as a subport; letting qt4-mac dependent ports pick what they want to depend on? Regards, Bradley Giesbrecht (pixilla)
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
