What's the procedure if I want to rename a port? I've been meaning to install ViewVC on my Mac since forever, and now that I finally have some free time, I thought I'd give it a shot, and realized it would be good to have a port for it. And in fact there is a port for ViewCVS, the old name of ViewVC, but it's old and not maintained. I'd like to try to update it, but the first step would be to rename it from viewcvs to viewvc. Do I just "cd dports/devel && svn mv viewcvs viewvc" or should we keep the viewcvs port around with a note about the name change? I note that the ethereal port still exists even though that project has been renamed wireshark. What's the recommended way to handle this situation? Is it documented somewhere?
On Nov 2, 2006, at 4:37 PM, Ryan Schmidt wrote:
What's the recommended way to handle this situation? Is it documented somewhere?
I don't think we have a fixed policy (and if we do, it was developed before we switched to subversion, so we didn't have svn mv available). 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. -- Daniel J. Luke +========================================================+ | *---------------- dluke@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
On Nov 2, 2006, at 3:46 PM, Daniel J. Luke wrote:
On Nov 2, 2006, at 4:37 PM, Ryan Schmidt wrote:
What's the recommended way to handle this situation? Is it documented somewhere?
I don't think we have a fixed policy (and if we do, it was developed before we switched to subversion, so we didn't have svn mv available).
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? 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? Chris
On Nov 2, 2006, at 5:25 PM, cssdev@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@geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
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@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@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@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev
Randall Wood rhwood@mac.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."
participants (4)
-
cssdev＠mac.com
-
Daniel J. Luke
-
Randall Wood
-
Ryan Schmidt