On Jul 16, 2011, at 10:24 PM, Blair Zajac wrote: > > On Jul 16, 2011, at 5:44 PM, Ryan Schmidt wrote: >> Also, this is not the first time this issue has come up; every other major >> version upgrade for subversion has had the same issue: working copy formats >> could change, and subversion will auto-update the working copy to the new >> format, breaking things for users who share working copies between different >> versions of subversion. And we haven't had any discussions about (or >> requests for) new subversion ports for older versions before (that I've >> seen). > > 1.7 will not auto-upgrade working copies.
my plan was to update the subversion port (and bindings ports) to 1.7 when it is released. If there is demand for a 1.6 port I will either create a subversion16 port, or someone else can do it. My gut feeling is that we won't really have any requests for 1.6 -- Daniel J. Luke +========================================================+ | *---------------- [email protected] ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+ _______________________________________________ macports-dev mailing list [email protected] http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
