Difference between revisions of "HowToCWS"
From Apache OpenOffice Wiki
(→HowToCWS using Subversion) |
(→Workflow: Empty numbered list items lead to the strange effect of transparently overwritten numbers, use nbsp instead.) |
||
| Line 24: | Line 24: | ||
# Note the '-s' flag that tags the CWS as subversion enabled | # Note the '-s' flag that tags the CWS as subversion enabled | ||
# The '-c' flag checks out that module into your tree. If you already had a subversion 'sc' directory you could omit the flag and use the faster 'switch' operation. | # The '-c' flag checks out that module into your tree. If you already had a subversion 'sc' directory you could omit the flag and use the faster 'switch' operation. | ||
| − | # | + | # |
# cwsresync supports in place resync using Subversion. You can always revert or modify the changes before commit | # cwsresync supports in place resync using Subversion. You can always revert or modify the changes before commit | ||
| − | # | + | # |
| − | # | + | # |
# Pick any temp dir you want | # Pick any temp dir you want | ||
# cwsanalyze (and cwsintegrate) extract the CWS changes and analyze/integrate against the CVS head. This is the point where a Subversion CWS is merged back into the upstreams CVS repository. | # cwsanalyze (and cwsintegrate) extract the CWS changes and analyze/integrate against the CVS head. This is the point where a Subversion CWS is merged back into the upstreams CVS repository. | ||
Revision as of 21:10, 15 December 2007
Contents
HowToCWS using Subversion
NB: This page is about working with the OpenOffice.org ChildWorkSpace (CWS) commit process using Subversion as the version control system. The workflow described here is used by many community developers but some Sun engineers might find it interesting as well.
For 'standard' Childworkspace handling please see CWS.
Quickstart
Workflow
Prerquisites: You have your CWS system setup for Subversion support and a MixedTree without the sc module.
1 export CWS_WORK_STAMP=<your_username>svntest01 2 cwscreate -s SRC680 m180 $CWS_WORK_STAMP 3 cwsadd -c sc 4 echo // Replace this with hacking| cat sc/source/filter/excel/biffdump.cxx - 5 cwsresync -m m181 sc 6 cwsresync -c sc 7 cwsresync -l m181 8 mkdir /tmp/__analyze_$(CWS_WORK_STAMP); cd /tmp/__analyze_$(CWS_WORK_STAMP) 9 cwsanalyze sc
Comments:
- Required for correct operation of the cws* tools
- Note the '-s' flag that tags the CWS as subversion enabled
- The '-c' flag checks out that module into your tree. If you already had a subversion 'sc' directory you could omit the flag and use the faster 'switch' operation.
- cwsresync supports in place resync using Subversion. You can always revert or modify the changes before commit
- Pick any temp dir you want
- cwsanalyze (and cwsintegrate) extract the CWS changes and analyze/integrate against the CVS head. This is the point where a Subversion CWS is merged back into the upstreams CVS repository.
Setup for existing CWS users
- Install Subversion from the Subversion site or use the one included with your distribution. Warning: Cygwin SVN is broken and will not work!.
- Add these lines to your .cwsrc:
# Subversion server root SVN_SERVER_ROOT=https://ooo-svn.osuosl.org
