[MacPorts] CommittersTipsAndTricks modified
MacPorts
noreply at macports.org
Fri May 29 12:22:20 PDT 2009
Changed page "CommittersTipsAndTricks" by dweber at macports.org from 206.176.233.162*
Page URL: <http://trac.macports.org/wiki/CommittersTipsAndTricks>
Diff URL: <http://trac.macports.org/wiki/CommittersTipsAndTricks?action=diff&version=19>
Revision 19
-------8<------8<------8<------8<------8<------8<------8<------8<--------
Index: CommittersTipsAndTricks
=========================================================================
--- CommittersTipsAndTricks (version: 18)
+++ CommittersTipsAndTricks (version: 19)
@@ -28,33 +28,44 @@
To create your own users directory:
{{{
-svn mkdir https://svn.macports.org/repository/macports/users/<YourMacPortsUserID>
+svn mkdir https://svn.macports.org/repository/macports/users/<YourMacPortsUserName>
}}}
Then, checkout your user directory:
{{{
-$ mkdir -p ~/myports
-$ svn co https://svn.macports.org/repository/macports/users/<YourMacPortsUserID> ~/myports
+$ svn co https://svn.macports.org/repository/macports/users/<YourMacPortsUserName> ~/myports
}}}
Then edit your MacPorts sources.conf file {{{/opt/local/etc/macports/sources.conf}}} to add ~/myports to the list before the main rsync source at rsync.macports.org, e.g.:
{{{
-file:///Users/<YourSystemUserID>/myports
+file:///Users/<YourSystemUserName>/myports
}}}
-To work on a copy of a port from MacPorts trunk, use {{{svn copy}}}. For example, to test changes on the cableswig port:
+To work on a copy of a port from MacPorts trunk, use `svn copy`. For example, to test changes on the cableswig port, you can copy the repository trunk (at the HEAD revision) to your new user branch:
{{{
-$ svn mkdir ~/myports/devel/cableswig
-$ svn copy https://svn.macosforge.org/repository/macports/trunk/dports/devel/cableswig/Portfile ~/myports/devel/cableswig/Portfile
+$ svn mkdir ~/myports/devel
+$ svn copy https://svn.macosforge.org/repository/macports/trunk/dports/devel/cableswig ~/myports/devel/
}}}
-Run `portindex` in `~/myports` any time you add a new Portfile, e.g.:
+Another option for a large branch is to copy everything at the server side, where the copy is equivalent to a unix hard link in the file system; e.g.:
+{{{
+$ svn mkdir https://svn.macports.org/repository/macports/users/<YourMacPortsUserName>/devel
+$ svn copy \
+ https://svn.macosforge.org/repository/macports/trunk/dports/devel/cableswig \
+ https://svn.macports.org/repository/macports/users/<YourMacPortsUserName>/devel/cableswig \
+ -m "testing modifications to cableswig"
+$ cd ~/myports
+$ svn update
+}}}
+
+After the copy, run `portindex` in `~/myports` (do this any time you add a new Portfile), e.g.:
{{{
$ cd ~/myports
+$ svn update
$ portindex
$ port file cableswig
}}}
-------8<------8<------8<------8<------8<------8<------8<------8<--------
* The IP shown here might not mean anything if the user or the server is
behind a proxy.
--
MacPorts <http://www.macports.org/>
Ports system for Mac OS
This is an automated message. Someone at http://www.macports.org/ added your email
address to be notified of changes on CommittersTipsAndTricks. If it was not you, please
report to .
More information about the macports-changes
mailing list