On Sun, 15 Jul 2007 12:23:48 +0200 Bart Martens <bartm@debian.org> wrote: > On Sun, 2007-07-15 at 10:33 +0100, Neil Williams wrote: > > I think it is easier for everyone if every change > > during sponsorship gets a new Debian version, so if you need me to > > sponsor packages, each upload to mentors.debian.net must use a new > > Debian version. > > That makes debian/changelog written by newbie packagers needlessly > long. Why is the length of the changelog of concern? If the same items are detailed overall, it is only three extra lines per change - one for the version line, one blank, one timestamp. I'm all for 'small is good, tiny is best' in an embedded context but then we drop the entire debian/changelog - I see little reason to worry about the length of debian/changelog in a Debian package. > I would regret that this would be enforced at mentors (I know, you did > not suggest that). True, I see no reason to make this a blanket change. Just me. > I prefer only one added block in debian/changelog > per upload to Debian, although I allow multiple blocks if the packager > wants that. e.g. in emdebian-tools, new versions are uploaded to Emdebian (v0.2.x) and new releases are uploaded to Debian (v0.x.0). It's specialised, yes, but it is perfectly usable by specifying the -v option to dpkg-buildpackage (via debuild or pdebuild if required). That way, all bugs closed in the changelog are closed with the Debian upload. (Emdebian does not have a BTS of our own.) Similarly, when using multiple mentor versions, it is just a case of collating those versions into the .changes file using -v. -- Neil Williams ============= http://www.data-freedom.org/ http://www.nosoftwarepatents.com/ http://www.linux.codehelp.co.uk/
Attachment:
pgp8X6URsx0iX.pgp
Description: PGP signature