Renaming a port

[Randall Wood]

A couple of months ago I moved the abiword2 port to abiword-x11

Take a look at the last version of the abiword2 port for how I made  
an update switch the ports.

On 2 Nov 2006, at 18:21, Daniel J. Luke wrote:

> On Nov 2, 2006, at 5:25 PM, cssdev at mac.com wrote:
>>> I would vote to just svn mv it and check in an updated portfile,  
>>> but I could see where an argument could be made to make it easier  
>>> for users who only do 'port upgrade' to know what is going on.
>>
>> What about adding a ui_error message indicating that the old port  
>> has been renamed?
>
> That was what I was thinking of for the case where we left the  
> existing port there for a while.
>
> The port's description should probably be changed to indicate that  
> it's old, been replaced by the newer port, and will be going away  
> in the future too.
>
>> Users would need to deactivate the old port before attempting to  
>> build or install the new one. Could that be somehow automated as a  
>> part of port upgrade?
>
> The current upgrade code doesn't have any hooks that would enable  
> that sort of behavior.
> --
> Daniel J. Luke
> +========================================================+
> | *---------------- dluke at geeklair.net ----------------* |
> | *-------------- http://www.geeklair.net -------------* |
> +========================================================+
> |   Opinions expressed are mine and do not necessarily   |
> |          reflect the opinions of my employer.          |
> +========================================================+
>
>
> _______________________________________________
> macports-dev mailing list
> macports-dev at lists.macosforge.org
> http://lists.macosforge.org/mailman/listinfo/macports-dev


Randall Wood
rhwood at mac.com

"The rules are simple: The ball is round. The game lasts 90 minutes.  
All the
rest is just philosophy."