Hallo *.
I have cvs 1.11.1p1 on a debian woody and i use WinCvs 2.0.0.2 as a
client on my windows pc.
I'm a beginner in cvs, but till now i can use it quite fine after
reading the fine manuals...
This week i discover administrative files and i'm trying to use them
(i'm also root on debian, so i have the force!)
I have two question about them.
First one:
I've modified my 'modules' file to match modules under cvs so users in
WinCvs can list them during the checkout.
Now i read somewhere that i can handle administrative files as a module
under cvs just checking out the module CVSROOT.
I tried and it works (except for some problems due to file permission in
debian), but.
But if i check out the module CVSROOT and i try to edit my local copy of
'modules' file it doesn't match the file i can see on the server.
The file on the server is this:
---SNIP---
Consulente1:/usr/local/cvs/CVSROOT# cat modules
# Three different line formats are valid:
# key -aaliases...
# key [options] directory
# key [options] directory files...
#
# Where options are composed of:
# -i prog Run prog on cvs commit from top-level of module.
# -o prog Run prog on cvs checkout of module.
# -e prog Run prog on cvs export of module.
# -t prog Run prog on cvs rtag of module.
# -u prog Run prog on cvs update of module.
# -d dir Place module in directory dir instead of
module name.
# -l Top-level directory only -- do not recurse.
#
# NOTE: If you change any of the Run options above, you'll have to
# release and re-checkout any working directories of these modules.
#
# And directory is a path to a directory relative to $CVSROOT.
#
# The -a option specifies an alias. An alias is interpreted as if
# everything on the right of the -a had been typed on the command line.
#
# You can encode a module within a module by using the special ''
# character to interpose another module into the current module. This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.
#Russia Russia
#Generico Generico
#filesystem filesystem
#PleasureX PleasureX
#Team Team
#BOOT BOOT
#Telco142 Telco142
Consulente1:/usr/local/cvs/CVSROOT#
---PINS---
and the local copy on my pc after checking out CVSROOT module is this:
---SNIP---
# Three different line formats are valid:
# key -aaliases...
# key [options] directory
# key [options] directory files...
#
# Where options are composed of:
# -i prog Run prog on cvs commit from top-level of module.
# -o prog Run prog on cvs checkout of module.
# -e prog Run prog on cvs export of module.
# -t prog Run prog on cvs rtag of module.
# -u prog Run prog on cvs update of module.
# -d dir Place module in directory dir instead of
module name.
# -l Top-level directory only -- do not recurse.
#
# NOTE: If you change any of the Run options above, you'll have to
# release and re-checkout any working directories of these modules.
#
# And directory is a path to a directory relative to $CVSROOT.
#
# The -a option specifies an alias. An alias is interpreted as if
# everything on the right of the -a had been typed on the command line.
#
# You can encode a module within a module by using the special ''
# character to interpose another module into the current module. This
# can be useful for creating a module that consists of many directories
# spread out over the entire source repository.
---PINS---
It differs in some comment line and the local copy doesn't have the
module i've added by hand in the past.
Why?
Second question: as you can see before, i've added some modules by hand,
but they are single-word modules, but i also have some modules i want to
keep under cvs whith names made by two or more word: something like
'project 1' or 'test suite product X'; windows allows (more or less...)
to use spaces in filenames, so people here abuse them and i cannot tell
them to use underscore instead.
I wasn't able to set up a modules file to match this kind of project. I
have to remember their names to checkout them in WinCvs. I also tried to
use -a to set an alias, but i miss something...
Can i use modules file to list this kind of projects?
Someone can give me some hints on how to well manage that files?
Thanks in advance.
--
manuel 'fmf' ferrero | http://www.servidellagleba.it/~manuel/blog/
Run out of taglines: (A)bort (R)eread (S)teal
___
Info-cvs mailing list
Info-cvs@gnu.org
http://lists.gnu.org/mailman/listinfo/info-cvs
