Re: problems managing package with CVS
>>"Chris" == Chris Ruffin <c.ruffin@ieee.org> writes:
Chris> I wonder why the author of these tools chose to leave cvs-co-upgrade
Chris> as a separate process. It seems to me like it should be integrated
Chris> into cvs-upgrade.
'Cause I did not trust cvs-co-upgrade to do the right thing in
all cases (indeed, as some people have pointed out, cvs should do the
right thing by itself anyway). Human oversight, in my opinion, was
required, so cvs-co-upgrade just provides a sanity check that humans
can then use to bring their checked out dirs into synch.
manoj
--
Suppose for a moment that the automobile industry had developed at
the same rate as computers and over the same period: how much cheaper
and more efficient would the current models be? If you have not
already heard the analogy, the answer is shattering. Today you would
be able to buy a Rolls-Royce for $2.75, it would do three million
miles to the gallon, and it would deliver enough power to drive the
Queen Elizabeth II. And if you were interested in miniaturization,
you could place half a dozen of them on a pinhead. Christopher Evans
Manoj Srivastava <srivasta@debian.org> <http://www.debian.org/%7Esrivasta/>
1024R/C7261095 print CB D9 F4 12 68 07 E4 05 CC 2D 27 12 1D F5 E8 6E
1024D/BF24424C print 4966 F272 D093 B493 410B 924B 21BA DABB BF24 424C
Reply to: