Hello, Greg!
> > I see that I should not have used those particular file names in my request.
> > We are *not* dealing with C++ (or C) source files. Think instead of files
> > "foofoo.x" and "foofoo.y" where we want the two names to refer to the same
> > file.
> > This is a legacy situation here and so our options are more limited than one
> > would like.
>
> Then put another layer between CVS and your legacy situation. I.e. a
> layer that can create the links the underlying layer needs. I.e. write
> a little script that you can run every time before you do whatever you
> do with the files.
As far as I understand, that guy works on Windows and Machintosh. While
I'm pretty sure that both of those systems have some kind of "symlinks" on
the GUI level, I'm not sure whether the compilers can be persuaded to
dereferense those links.
I'm sure that the problem can be solved with some wrappers around the
compiler and a rule for developers on one of the platforms - "don't ever
edit *.x, edit *.y only"
Another question is that a generic intermediate level would be a very nice
thing to have. I imagine it as a bridge between the repository that stores
"versioned objects" and a build system that wants files with specific
names, specific line endings and in a specific encoding. But probably I
want too much.
Regards,
Pavel Roskin
