Re: CVS directories in debian packages
>>"Ola" == Ola Lundqvist <email@example.com> writes:
Ola> On Fri, May 17, 2002 at 11:01:21PM -0500, Manoj Srivastava wrote:
>> 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).
Ola> Well you assume that all source packages are from an external
Ola> upstream. That is not always the case. In fact many of the
Ola> packages I maintain (like java-common, harden etc) is generated
Ola> from a cvs dir. It is very convenient. How can you exclude the
Ola> CVS dirs from the source package then?
*ALL* my packages come from local CVS, including the one I am
upstream on, None of them contain CVS dirs. Indeed, saying you are
keeping sources in CVS is no excuse for not following guidelines laid
out in CVS docs, even.
Ola> Well I can export on every build but that takes quite a lot of time.
Ola> I like to build from the normal cvs dir.
I have not found that to be the case. cvs-buildpackage takes
marginally more time than dpkg-buildpackage, but not perceptibly so.
Sounds like you are saying you are too lazy to do the right thing.
Pick another fortune cookie.
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