Per module/file versioning

I have such an unusual case for versioning. I'm going to describe the use
cases.
We have a set of Cobol programs which, for simplicity and convenience are
wanted to be versioned by file.
For instance:
/Cobol/Prog1.COB
/Cobol/Prog2.COB
and so on.

The current procedure (manual), does increase by one the version each time
that the file changes (ala VMS filesystem and CVS). I'm not able to
replicate this under subversion since the versioning model is different.

The other case is to be able to have an independent revision number for each
module.
So /root/projectA/ and /root/projectB/ have each their own set of versions.
This is also something that cannot be done under Subversion, for what I
understand. However I've been reading about svn:externals but I seem unable
to not identify it's use on my case.

Anyone has been on the same situation? There's another approach I can have
to get the same goals (say that user knows that Prog1.COB:2 is the second
version of Prog1.COB and Prog2.COB:5 is the 5th version of Prog2.COB).

thanks
Received on Wed Sep 19 00:25:08 2007