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.
--
Kind regards,
+--------------------------------------------------------------------+
| Bas Zoetekouw | GPG key: 0644fab7 |
|----------------------------| Fingerprint: c1f5 f24c d514 3fec 8bf6 |
| [EMAIL PROTECTED], [EMAIL PROTECTED] | a2b1 2bae e41f 0644 fab7 |
+--------------------------------------------------------------------+
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
