Re: CVS directories in debian packages
>>"Bernhard" == Bernhard R Link <email@example.com> writes:
Bernhard> While I think this is true for finished packages, I think having
Bernhard> CVS in an source-package can make sense for experimental packages
Bernhard> to be shared between an group of people. Beeing able to
Bernhard> unpack it and first update it to the newest upstream-version
Bernhard> is quite nice. (There are other possiblities for it, but I think
Bernhard> this has it's uses).
Let me see.
a) If you have your CVS repository local to you your ./CVS/Root would
contain a local file path, and would be useless to people not on
the same machine, whether or not you have remote access to your
b) If you have remote access to your repository, why are people not
using that directly? Why must they go through untarring the
c) You anre now locking out anyone who may want to use a local
repository and send you patches from known, released versions.
So, if you have a central, distributed repository, having
direct access is better (allows checkin), and the CVS dirs in sources
do not add much; but seriously hampers people who may want revision
control, but not your repository.
When these grey bones are cast aside like gourds in autumn, what
pleasure will there be in looking at them? 149
Manoj Srivastava <firstname.lastname@example.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
To UNSUBSCRIBE, email to email@example.com
with a subject of "unsubscribe". Trouble? Contact firstname.lastname@example.org