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 +========================================================+ | *---------------- [EMAIL PROTECTED] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+
PGP.sig
Description: This is a digitally signed message part
_______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo/macports-dev
