Re: Bug#20499: cvs-buildpackage: doesn't handle symlinks in debian only packages
Hi,
>>"Adam" == Adam P Harris <apharris@burrito.onshore.com> writes:
Adam> Maybe at some point I'll take a look at the general problem of
Adam> transparent symlink handling native in CVS. I have some
Adam> connections at Cyclic who may have something to offer. Does
Adam> anyone have any communication already with Cyclic developers
Adam> about this?
Way back in 94/95 (when I was involved [in a minor way] with
CVS development) there was this talk about the great CVS dir database
rewrite, which would handle symlinks, and rewrite the attics
hack. This has never happened, since it is a rather major
undertaking.
Until this is done, cvs relies on RCS to handle archival of
files; and RCS deos not do symlinks at all.
However, I see there is a new CVS in the incoming directory,
which says it removed the diff/rcs dependencies. Hmm. Maybe it did do
all that was promised. Nope:
`L FILE'
The file is a symbolic link; `cvs import' ignores symbolic links.
People periodically suggest that this behavior should be changed,
but if there is a consensus on what it should be changed to, it
doesn't seem to be apparent. (Various options in the `modules'
file can be used to recreate symbolic links on checkout, update,
etc.; *note modules::..)
Anyway, I shall implement the warnings.
manoj
--
"Our reruns are better than theirs." Nick at Nite
Manoj Srivastava <srivasta@acm.org> <http://www.datasync.com/%7Esrivasta/>
Key C7261095 fingerprint = CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
--
To UNSUBSCRIBE, email to debian-devel-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Reply to: