Re: libmail-spf-query-perl 1.999-1 prepared for upload
Russ Allbery dijo [Thu, Feb 09, 2006 at 11:54:15AM -0800]:
> > BTW, I'll see if I can package some additional packages from the
> > "Modules To Package" list soon. Adopting the listed
> > courier-filter-perl package (written by me) for the pkg-perl group would
> > be one of my top priorities. Also, I see that the pkg-perl group's
> > Subversion guide (/website/ subversion.pod) has a gap in the
> > description of how to upgrade to new upstream versions. Having learned
> > today how that works, I volunteer to fill in that section if nobody
> > objects.
> Oh, speaking of the Subversion guide, it also contradicts itself about how
> releases should be tagged. In one place it says to use debian_version
> tags, but in another place it says that svn-buildpackage --svn-tag should
> be used. The latter just creates a tag equal to the version number,
> without the debian_version prepended.
> I'd rather go with the svn-buildpackage behavior; the debian_version part
> of the tag name never seemed that useful. But we should probably clarify
> it one way or the other (and a bunch of the packages I've uploaded have
> the svn-buildpackage tags from before I noticed that difference).
Hmh... Here, I'd go the other way - Yes, maybe I'm sloppy, but I often
build thinking I'm done, then go check the package is properly built,
lintian-clean, yada yada, and go back to do some changes. Of course, I
_only_ tag as the step after sending the built package to ftp-master.
In fact, I also don't follow the instructions to the letter - What I
prefer doing is (as it's incredibly shorter) "svn copy trunk
The effect is the same, no matter what you do. It should be fixed,
yes. But it should point to the possible alternatives.
Gunnar Wolf - email@example.com - (+52-55)5623-0154 / 1451-2244
PGP key 1024D/8BB527AF 2001-10-23
Fingerprint: 0C79 D2D1 2C4E 9CE4 5973 F800 D80E F35A 8BB5 27AF