/[meta-cvs]/meta-cvs/F-F1216688DF5C31C04736DBD403342A77
ViewVC logotype

Diff of /meta-cvs/F-F1216688DF5C31C04736DBD403342A77

Parent Directory Parent Directory | Revision Log Revision Log | View Patch Patch

revision 1.6 by kaz, Fri Mar 15 18:11:58 2002 UTC revision 1.7 by kaz, Sun Jun 23 19:18:11 2002 UTC
# Line 91  Line 91 
91    4.1  Creating a Module    4.1  Creating a Module
92    
93        The only way to create a Meta-CVS module is to have an existing set        The only way to create a Meta-CVS module is to have an existing set
94        of files, or an empty directory, and import it using the import command.        of files, or an empty directory, and invoke the create command
95        The steps are:        in the top level directory.
96    
97        1. Change to the topmost directory of the file tree that you want to        1. Change to the topmost directory of the file tree that you want to
98           import.           place under Meta-CVS.
99    
100        2. Invoke        2. Invoke
101    
102             mcvs import <module-name> <vendor-tag> <release-tag>             mcvs create <module-name> <vendor-tag> <release-tag>
103    
104           The <module-name> specifies what your module will be called; it           The <module-name> specifies what your module will be called; it
105           need not be the same as the name of the top level directory.           need not be the same as the name of the top level directory.
106           When later you check out the module, you will have to specify that           When later you check out the module, you will have to specify that
107           name, and by default a directory of that name will be created.           name, and by default a directory of that name will be created.
108    
109           The <vendor-tag> and <release-tag> are artifacts of CVS import;           The <vendor-tag> and <release-tag> are artifacts of cvs import,
110           they must be specified. The vendor-tag is used by CVS to tag           which is the command that Meta-CVS uses to create the CVS repository for the
111           the vendor branch on which the import takes place. The release-tag           new project. These arguments must be specified. The vendor-tag is used
112           tags all the newly imported file revisions.           by CVS to tag the vendor branch on which the import takes place. The
113             release-tag tags all the newly imported file revisions.
114     (!)   Note that vendor branch imports do not work in Meta-CVS at all;  
115           each import creates a new unique set of files, so doing multiple     (!)   Note that CVS vendor branches do not work in Meta-CVS;
116           imports over the same Meta-CVS module will *not* work like it           each mcvs create operation creates a new unique set of files, so doing
117           does in CVS. As a workaround, if you want to synchronize with third           multiple imports over the same Meta-CVS module will *not* work like it
118           party sources, you can do so manually using ordinary branches.           does in CVS. As a workaround, if you want to synchronize with third
119             party sources, you can do so manually using ordinary branches.
120    
121        3. If your file tree contains any files whose names have suffixes,        3. If your file tree contains any files whose names have suffixes,
122           Meta-CVS will gather a list of these suffixes and bring up a text           Meta-CVS will gather a list of these suffixes and bring up a text
# Line 139  Line 140 
140            editor so that you can specify an import comment. This part should            editor so that you can specify an import comment. This part should
141            be familiar to the CVS user.            be familiar to the CVS user.
142    
143        5.  The module should now be imported, and is ready to be checked out.        5.  The module should now be created, and is ready to be checked out.
144    
145        Note that Meta-CVS does not store empty directories at all. This behavior        Note that Meta-CVS does not store empty directories at all. This behavior
146        differs from CVS in a subtle way. With CVS, you can create an empty        differs from CVS in a subtle way. With CVS, you can create an empty
# Line 153  Line 154 
154    
155        Thus, if you wish to create a new empty project, don't bother making a        Thus, if you wish to create a new empty project, don't bother making a
156        multi-level directory tree. Just create one empty directory with no        multi-level directory tree. Just create one empty directory with no
157        subdirectories, and invoke mcvs import in that directory. It will be        subdirectories, and invoke mcvs create in that directory. It will be
158        easy to add directories later. Under Meta-CVS, the add command is        easy to add directories later. Under Meta-CVS, the add command is
159        recursive if you specify -R, unlike under CVS which requires directories        recursive if you specify -R, unlike under CVS which requires directories
160        to be added individually, and then files. The Meta-CVS add command also        to be added individually, and then files. The Meta-CVS add command also
161        identifies any new file suffixes and prompts you to edit how they        identifies any new file suffixes and prompts you to edit how they
162        will be handled, similarly to the import command.        will be handled, similarly to the create command.
163    
164    
165    4.2  Checking Out a Module    4.2  Checking Out a Module

Legend:
Removed from v.1.6  
changed lines
  Added in v.1.7

  ViewVC Help
Powered by ViewVC 1.1.5