[pkgsrc/trunk]: pkgsrc/devel/p5-ShipIt Initial import of p5-ShipIt version 0....

[seb <seb%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/097d5e130cb5
branches:  trunk
changeset: 548752:097d5e130cb5
user:      seb <seb%pkgsrc.org@localhost>
date:      Wed Oct 22 18:40:54 2008 +0000

description:
Initial import of p5-ShipIt version 0.52 in the NetBSD Packages
Collection.

Releasing a new version of software (Perl module) takes a lot of
steps... finding the next version number (and making sure you didn't
already use that version number before), making sure your changelog
is updated, making sure your "make dist" results in a tarball that
builds, commiting changes (with updated version number), tagging,
and uploading the tarball somewhere.  Or maybe more steps. Or not
some of the above. Maybe you forgot something! And maybe you manage
multiple projects, and each project has a different release process.
You want to be hacking, not jumping through hoops.  Your contributors
want to see their patches actually make it into a release, which
won't happen if you're afraid of releases.  shipit automates all
the hell. It makes life beautiful.

diffstat:

 devel/p5-ShipIt/DESCR    |  13 +++++++++++++
 devel/p5-ShipIt/Makefile |  19 +++++++++++++++++++
 devel/p5-ShipIt/distinfo |   5 +++++
 3 files changed, 37 insertions(+), 0 deletions(-)

diffs (49 lines):

diff -r 3a70bf792bf3 -r 097d5e130cb5 devel/p5-ShipIt/DESCR
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/p5-ShipIt/DESCR     Wed Oct 22 18:40:54 2008 +0000
@@ -0,0 +1,13 @@
+Releasing a new version of software (Perl module) takes a lot of
+steps... finding the next version number (and making sure you didn't
+already use that version number before), making sure your changelog
+is updated, making sure your "make dist" results in a tarball that
+builds, commiting changes (with updated version number), tagging,
+and uploading the tarball somewhere.
+Or maybe more steps. Or not some of the above. Maybe you forgot
+something! And maybe you manage multiple projects, and each project
+has a different release process.
+You want to be hacking, not jumping through hoops.
+Your contributors want to see their patches actually make it into
+a release, which won't happen if you're afraid of releases.
+shipit automates all the hell. It makes life beautiful.
diff -r 3a70bf792bf3 -r 097d5e130cb5 devel/p5-ShipIt/Makefile
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/p5-ShipIt/Makefile  Wed Oct 22 18:40:54 2008 +0000
@@ -0,0 +1,19 @@
+# $NetBSD: Makefile,v 1.1.1.1 2008/10/22 18:40:54 seb Exp $
+#
+
+DISTNAME=              ShipIt-0.52
+PKGNAME=               p5-${DISTNAME}
+CATEGORIES=            devel perl5
+MASTER_SITES=          ${MASTER_SITE_PERL_CPAN:=../../authors/id/B/BR/BRADFITZ/}
+
+MAINTAINER=            pkgsrc-users%NetBSD.org@localhost
+HOMEPAGE=              http://search.cpan.org/dist/ShipIt/
+COMMENT=               Perl software release tool
+
+PKG_DESTDIR_SUPPORT=   user-destdir
+
+USE_LANGUAGES= # empty
+PERL5_PACKLIST=        auto/ShipIt/.packlist
+
+.include "../../lang/perl5/module.mk"
+.include "../../mk/bsd.pkg.mk"
diff -r 3a70bf792bf3 -r 097d5e130cb5 devel/p5-ShipIt/distinfo
--- /dev/null   Thu Jan 01 00:00:00 1970 +0000
+++ b/devel/p5-ShipIt/distinfo  Wed Oct 22 18:40:54 2008 +0000
@@ -0,0 +1,5 @@
+$NetBSD: distinfo,v 1.1.1.1 2008/10/22 18:40:54 seb Exp $
+
+SHA1 (ShipIt-0.52.tar.gz) = 66dbf51a9e6afbaef0a6b68c2f8b55febbf024da
+RMD160 (ShipIt-0.52.tar.gz) = 37a3bcd874c0657b76d2e3c3e4c4a2c39c705e86
+Size (ShipIt-0.52.tar.gz) = 16293 bytes