[31791] trunk/dports/devel

[Weissmann Markus]

On 07.12.2007, at 23:38, Daniel J. Luke wrote:

> On Dec 7, 2007, at 4:44 PM, Ryan Schmidt wrote:
>> I haven't looked at your changes and I don't know if the deadlock  
>> Markus describes will occur. But I have suggested a couple times  
>> that we should have a portfile keyword like "superseded_by" which  
>> can be used to indicate that a given port name is obsolete.  
>> Behavior of this keyword would be that anyone who has the port  
>> installed and uses port upgrade sees this port as needing to be  
>> upgraded. Anyone who attempts to upgrade this port gets a message  
>> that they need to uninstall this port and install this other port.
>
> You can achieve this now with a pre-fetch ui_msg (and bumping the  
> revision of the port that you want to remove).
>
>> Once those steps are implemented and released, we could look into  
>> more elegant solutions including MacPorts automatically  
>> uninstalling the old port and installing the new one with the same  
>> variants or something, but I don't think that's essential.
>
>
> That might be an interesting project for someone, but given that  
> this doesn't happen that often, I don't think any of the people who  
> normally develop stuff for base are working on it.
>


Yes. Thats exactly what I wanted to say. And also perhaps that yes,  
the deadlock will occur.


Regards,

-Markus

---
Dipl. Inf. (FH) Markus W. Weissmann
http://www.mweissmann.de/
http://www.macports.org/