Sidestepping the issue of links in CVS, I'm unclear on the problem
you're trying to solve.
We have a number of perl scripts stored in CVS which share a large set
of common library modules. They work exactly as you describe, in that
they are able to bootstrap themselves onto any machine they are
Ok, suppose you have a driver script, call it 'bootstrap.p'.
This driver script
goes along with a couple of data files (say an ini file and a
function
library that drives the script (call it instructions.pl)
Now, where should bootstrap.p live? If it lives in a
centralized script
Title: RE: Verifymsg on branches?
Uwe,
I've just finished my first cut at doing per-branch bug number requirements in our CVS repository. Bear in mind I haven't finished testing it yet, so I could be way off base here. It also presumes you are using cvs client/server.
My solution was to
Title: Taginfo question
I've been looking for this myself, and I believe you are correct.
A few weeks ago (in August) one of the OpenAvenue developers posted a patch which provides branch info in taginfo (as well as other information I need in commitinfo, etc.). The patch was for the
