kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/devel/p5-ShipIt/Makefile

20 lines
503 B
Makefile
Raw Normal View History

Bump PKGREVISIONs for perl 5.30.0
2019-08-11 15:17:48 +02:00
# $NetBSD: Makefile,v 1.16 2019/08/11 13:20:19 wiz Exp $
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.
2008-10-22 20:40:54 +02:00
#
Update to 0.60 Upstream changes: 0.60 (2013-02-07) * Same as 0.59. Make it non TRIAL :) 0.59 (2013-02-07) * Support TRIAL release for PAUSE with --trial command line option 0.58 (2012-11-09) * Support our $VERSION = 'v1.0.0' construct per xdg 0.57 (2012-07-21) * Fixed an issue with PAUSE 0.56 (2012-07-21) * Supports and writes different style of perl version declarations (Brad Willis) * Changed the display of git unknown files to be prettier (Daniel LeWarne) * Include global git exclusion files (Daniel LeWarne) * Add support for not running under a terminal (Dave Lambley) * Make tilde (~) to point user's home directory (Dave Lambley) * miyagawa now takes over the maintenance of ShipIt
2015-04-05 15:12:11 +02:00
DISTNAME= ShipIt-0.60
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.
2008-10-22 20:40:54 +02:00
PKGNAME= p5-${DISTNAME}
Bump PKGREVISIONs for perl 5.30.0
2019-08-11 15:17:48 +02:00
PKGREVISION= 5
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.
2008-10-22 20:40:54 +02:00
CATEGORIES= devel perl5
Update to 0.60 Upstream changes: 0.60 (2013-02-07) * Same as 0.59. Make it non TRIAL :) 0.59 (2013-02-07) * Support TRIAL release for PAUSE with --trial command line option 0.58 (2012-11-09) * Support our $VERSION = 'v1.0.0' construct per xdg 0.57 (2012-07-21) * Fixed an issue with PAUSE 0.56 (2012-07-21) * Supports and writes different style of perl version declarations (Brad Willis) * Changed the display of git unknown files to be prettier (Daniel LeWarne) * Include global git exclusion files (Daniel LeWarne) * Add support for not running under a terminal (Dave Lambley) * Make tilde (~) to point user's home directory (Dave Lambley) * miyagawa now takes over the maintenance of ShipIt
2015-04-05 15:12:11 +02:00
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=../../authors/id/M/MI/MIYAGAWA/}
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.
2008-10-22 20:40:54 +02:00
MAINTAINER= pkgsrc-users@NetBSD.org
Update packages using a search.cpan.org HOMEPAGE to metacpan.org. The former now redirects to the latter. This covers the most simple cases where http://search.cpan.org/dist/name can be changed to https://metacpan.org/release/name. Reviewed by hand to hopefully make sure no unwanted changes sneak in.
2019-06-30 22:14:13 +02:00
HOMEPAGE= https://metacpan.org/release/ShipIt
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.
2008-10-22 20:40:54 +02:00
COMMENT= Perl software release tool
Updating devel/p5-ShipIt from 0.52 to 0.53 pkgsrc changes: - Add license definition Upstream changes: 0.53 (2009-12-15) * Mercurial support * Module::Build support
2010-03-17 00:05:01 +01:00
LICENSE= ${PERL5_LICENSE}
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.
2008-10-22 20:40:54 +02:00
USE_LANGUAGES= # empty
PERL5_PACKLIST= auto/ShipIt/.packlist
.include "../../lang/perl5/module.mk"
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink