This is one of CVS' biggest design flaws. No, you cannot check out the
original version of the module after the module's definition has been
changed. However, you can work around the problem by doing some kind of
ad hoc versioning within the module database, e.g. by creating modules
with names like "module1-version1", "module1-version2" and so on. Then
create a module alias to point to the most-often wanted version of the
module.
--- Forwarded mail from [EMAIL PROTECTED]
I understood that I can define modules in the module file and that cvs uses
the most recent version which is alway checked out in the repository. So
this file is used by every body who uses the repository.
Consider the following:
I released Version1 with a module module1 that consists of dir1 and dir2
While developing Version2 I droped dir2 and added dir3, i.e. module1
consists now of dir1 and dir3. This is now reflected in the current version
of the module file.
Can I still check out Version1 of modul1?
--- End of forwarded message from [EMAIL PROTECTED]
_______________________________________________
Info-cvs mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/info-cvs
