...
1. Checkout the trunk (svn co https://source.sakaiproject.org/svn/msub/uwo.ca/owl/trunk trunk)
2. Edit the .externals file
3. Commit the changes (svn commit .externals -m "modifying .externals")
4. Confirm the svn:externals property (svn propset svn:externals -F .externals .)
At this point you could run svn update and it would pull down all the code for the various tools in your Sakai implementation.
Western's custom tools
For customized tools, we use a structure where each tool has its own directory at the root, and trunk, branches, and tags directories underneath, like so:
- .../svn/msub/uwo.ca
- /site-manage
- /trunk
- /branches
- /tags
- /newTool1
- /trunk
- /branches
- /tags
- /site-manage
These tools might be custom versions of existing Sakai tools (ie. site-manage), or they might be brand new tools (ie. newTool1).
You've probably guessed by now that our modifications to .externals involve pointing some of the references to our custom tools. Here's how this looks:
| Code Block |
|---|
access https://source.sakaiproject.org/svn/access/branches/sakai-2.8.x
alias https://source.sakaiproject.org/svn/alias/branches/sakai-2.8.x
...
roster https://source.sakaiproject.org/svn/roster/branches/sakai-2.8.x
rwiki https://source.sakaiproject.org/svn/rwiki/branches/sakai-2.8.x
sections https://source.sakaiproject.org/svn/sections/branches/sakai-2.8.x
site https://source.sakaiproject.org/svn/site/branches/sakai-2.8.x
#site-manage https://source.sakaiproject.org/svn/site-manage/branches/sakai-2.8.x
syllabus https://source.sakaiproject.org/svn/syllabus/branches/sakai-2.8.x
...
site-manage https://source.sakaiproject.org/svn/msub/uwo.ca/site-manage/trunk
newTool1 https://source.sakaiproject.org/svn/msub/uwo.ca/newTool1/trunk
|
Note that the original site-manage reference has been commented out, and our new references have been placed at the bottom.