Bas Zoetekouw <[EMAIL PROTECTED]> writes: > Hi Jonathan! > > You wrote: > > > I'm the Debian maintainer for pksd, an OpenPGP keyserver. I've been > > asked by upstream if I want to maintain the debian/ directory in the > > project's CVS. The RPM .spec file is already done this way. Is there any > > good reason not to do this? > > I see very few problems with this, if you do it The Right Way[1]. > > > It will make things a lot easier for people > > pulling running CVS builds. The only drawback I can see is changes in > > the packaging between releases leads to a whole new src tarball to > > upload to the archive rather than just a new diff, but hopefully this > > shouldn't happen too often. > > That shouldn't be necessary, since you could just run a cvs up on the > debian/ dir alone. > > [1] The Right Way, IMHO, is using tags and branches. For each upstream > release, you could have a debian branch, containing only changes to > the debian/ dir. > Seconded. I once did a brief sum-up how I manage that, in case someone's interested, take a look at [2]
[2] http://lists.debian.org/debian-devel/2002/debian-devel-200209/msg02003.html Regards -- Andreas Rottmann | Dru@ICQ | 118634484@ICQ | [EMAIL PROTECTED] http://www.8ung.at/rotty | GnuPG Key: http://www.8ung.at/rotty/gpg.asc Fingerprint | DFB4 4EB4 78A4 5EEE 6219 F228 F92F CFC5 01FD 5B62 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
