Re: CVS directories in debian packages
>>"Joey" == Joey Hess <email@example.com> writes:
Joey> Can anyone think of a reason for a debian binary package to
Joey> include a CVS directory? I can't, and about 50 packages in
Joey> unstable do. For example, it crept into debhelper since I build
Joey> it out of a CVS tree, and a few copies of files into the
Joey> build dir are overly aggressive.
It make no sense for CVS directories in binary packages (at
best, it interferes with the users ability to put the dirs under
local CVS (I have /etc under CVS).
It does not make sense for source packages either; CVS
directories in source trees cause havoc when trying to later import
the sources into another CVS repository (for example, a user trying
to keep local modifications of debian sources in a local CVS).
Additionally, If one does not do a cvs export -kv for a
package, then the RCS strings would cause problems when further
trying to import your sources into another CVS repository
One often would like to use `-kv' with `cvs export'. This
causes any keywords to be expanded such that an import done at some
other site will not lose the keyword revision information.
I think, therefore, that CVS dirs should never leave the
developers machine, whether in binary, or in source packages.
Actually, it also looks like we should optimize (13,2,42,8,'hike')
into a pp_padav copy as well. Larry Wall in
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