[120349] trunk/base/portmgr/ReleaseProcess
jmr at macports.org
jmr at macports.org
Fri May 23 18:18:48 PDT 2014
Revision: 120349
https://trac.macports.org/changeset/120349
Author: jmr at macports.org
Date: 2014-05-23 18:18:47 -0700 (Fri, 23 May 2014)
Log Message:
-----------
fix ReleaseProcess instructions for creating the full archive, which broke with newer svn versions
Modified Paths:
--------------
trunk/base/portmgr/ReleaseProcess
Modified: trunk/base/portmgr/ReleaseProcess
===================================================================
--- trunk/base/portmgr/ReleaseProcess 2014-05-24 01:13:34 UTC (rev 120348)
+++ trunk/base/portmgr/ReleaseProcess 2014-05-24 01:18:47 UTC (rev 120349)
@@ -103,14 +103,13 @@
tag URL. For instance:
svn co [-r<rev>] https://svn.macports.org/repository/macports/trunk release_2.0.0-archive
- cd release_2.0.0-archive/base
- svn switch https://svn.macports.org/repository/macports/tags/release_2_0_0/base
+ cd release_2.0.0-archive
+ svn rm base
+ svn cp https://svn.macports.org/repository/macports/tags/release_2_0_0/base base
And finally we tag the entire directory as release_2_0_0-archive:
-FIXME: this doesn't seem to work any more. The base subdir in the tag ends up being from trunk.
-
- cd ../../
+ cd ..
svn cp -m "commit-message" release_2.0.0-archive https://svn.macports.org/repository/macports/tags/release_2_0_0-archive
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.macosforge.org/pipermail/macports-changes/attachments/20140523/ad6bb71e/attachment.html>
More information about the macports-changes
mailing list