[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: plan for code freeze

From: Sam Steingold
Subject: Re: plan for code freeze
Date: 29 Aug 2002 16:25:22 -0400
User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3.50

> * In message <address@hidden>
> * On the subject of "Re: plan for code freeze "
> * Sent on Thu, 29 Aug 2002 16:15:09 -0400
> * Honorable "Stefan Monnier" <monnier+gnu/address@hidden> writes:
> > > 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.

> 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


Sam Steingold (http://www.podval.org/~sds) running RedHat7.3 GNU/Linux
<http://www.camera.org> <http://www.iris.org.il> <http://www.memri.org/>
<http://www.mideasttruth.com/> <http://www.palestine-central.com/links.html>
There are two ways to write error-free programs; only the third one works.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]