Re: plan for code freeze

[Stefan Monnier]

> > > > CVS has special support for symlinks-in-the-repository, so it should
> > > > work, and if it doesn't, then CVS will tell you (I seem to remember that
> > > > there are limits to what CVS handles).
> > > > It is already used for emacs/src/regex.[ch] which is symlinked
> > > > with gnulib/regex.[ch].
> > > 
> > > this is a stunning revelation to me (I had some quite disastrous
> > > experience with symlinks in the CVS some years ago, and the CVS manual
> > > on the cvshome.org appears to support my understanding that symlink and
> > > CVS do not work together at all).
> > > 
> > > Could you please be more specific: how do symlinks work?
> > 
> > I think you confuse the issue of revision-control of symlinks
> > in your project, against using symlinks inside the repository.
> 
> nope - I have several identical files: FOO, src/BAR, etc/ZOT and I want
> them all to refer the the same file in the CVS repository (FOO,v).
> this caused so many problems that now each of these files has its own
> *,v RCS file.

What have you tried ?

> > But you can use symlinks inside the repository for purposes of
> > providing the same RCS file(s) under a few different names in the CVS
> > repository and such that updating one automatically updates the
> > other(s) (because they really are one and the same).
> 
> so how do I tell cvs to do
> 
> $ rm -f src/BAR,v
> $ ln -s FOO,v src/BAR,v

There is no such cvs command, you have to do it by hand (i.e. use the
two lines above).


        Stefan