[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[ale] CVS 'modules' 'style' and 'HOWTO' question
- Subject: [ale] CVS 'modules' 'style' and 'HOWTO' question
- From: jmmills at telocity.com (John Mills)
- Date: Mon, 4 Mar 2002 11:17:02 -0500 (EST)
After a deafeningly silent response on comp.software.config-mgmnt, I have
a question for CVS users here.
Multiple functions in my source tree contribute to one shared
'include/interface' directory in addition to having their own
I want to define CVS 'modules' for my source tree so a user can check out
source and header files associated with one function with only the needed
files from the 'include/interface' directory, as well as its own full set
of 'include/MODULE/*.h' and 'MODULE/*.[c|cpp]' files (and 'Makefile',
>>TERMINOLOGY NOTE: By "check out" I mean here "get a working copy", not
"lock files for editing". Locks would be applied on a per-file basis.<<
I do not get to reorganize the source tree, nor do I want to.
Can I define a CVS 'module' which includes only some of the files from one
directory (my 'include/interface/')? how? Reading CVS docs suggests I
can do it, but I have not been successful at this.
More broadly, does it make sense to split the checkout of a directory of
shared definitions like my 'include/interface' in the example, or does it
seem better to always treat 'include/interface' as a unit?
Thanks for general or specific comments.
- John Mills
This message has been sent through the ALE general discussion list.
See http://www.ale.org/mailing-lists.shtml for more info. Problems should be
sent to listmaster at ale dot org.