On Jun 22, 2011, at 19:38, Jeremy Lavergne wrote:
>> libnotify: Don't install on Lion
>>
>> Yes, I know it installs and runs fine, but when libnotify.dylib is present in
>> ${prefix}/lib, it causes problems when linking future binaries. This results
>> in miscelaneous build failures and runtime failures that are difficult to
>> diagnose.
>>
>> Rather than subject users to these problems, it is better to disable this
>> port
>> until we can come up with a good solution for Lion.
>
> How about test for the file then stop and alert the user about the situation.
> Suggest they force uninstall the previous one, clean, and install again.
>
> Should we also make note of this in Known Issues/Migration?
If that's the case, then add logic to the port to prevent its installation on
Lion and greater.
I don't think any additional documentation is necessary, as the Migration page
already sufficiently explains that upgrading from one OS to the next requires
reinstallation of everything.
_______________________________________________
macports-dev mailing list
[email protected]
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
