kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/mail/p5-IMAP-Admin/Makefile

19 lines
470 B
Makefile
Raw Normal View History

Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
# $NetBSD: Makefile,v 1.18 2006/03/04 21:30:01 jlam Exp $
Initial import of p5-IMAP-Admin-1.3.7, a perl module for basic IMAP server administration
2000-10-16 11:11:35 +02:00
#
Updated p5-IMAP-Admin to 1.6.1 - bug report/fix (thanks to Arkadi Shishlov and Oleg Gawrilof) for CRAM setting being uninitialized before use for the default case. - added error condition for CRAM capability, cram use wanted without fallback, but cram not available
2002-01-31 15:20:05 +01:00
DISTNAME= IMAP-Admin-1.6.1
Initial import of p5-IMAP-Admin-1.3.7, a perl module for basic IMAP server administration
2000-10-16 11:11:35 +02:00
PKGNAME= p5-${DISTNAME}
SVR4 packages have a limit of 9 chars for a package name. The automatic truncation in gensolpkg doesn't work for packages which have the same package name for the first 5-6 chars. e.g. amanda-server and amanda-client would be named amanda and amanda. Now, we add a SVR4_PKGNAME and use amacl for amanda-client and amase for amanda-server. All svr4 packages also have a vendor tag, so we have to reserve some chars for this tag, which is normaly 3 or 4 chars. Thats why we can only use 6 or 5 chars for SVR4_PKGNAME. I used 5 for all the packages, to give the vendor tag enough room. All p5-* packages and a few other packages have now a SVR4_PKGNAME.
2001-10-18 17:20:01 +02:00
SVR4_PKGNAME= p5iad
Bump the PKGREVISIONs of all (638) packages that hardcode the locations of Perl files to deal with the perl-5.8.7 update that moved all pkgsrc-installed Perl files into the "vendor" directories.
2005-08-06 08:19:03 +02:00
PKGREVISION= 2
Initial import of p5-IMAP-Admin-1.3.7, a perl module for basic IMAP server administration
2000-10-16 11:11:35 +02:00
CATEGORIES= mail perl5
MASTER_SITES= ${MASTER_SITE_PERL_CPAN:=IMAP/}
Point MAINTAINER to pkgsrc-users@NetBSD.org in the case where no developer is officially maintaining the package. The rationale for changing this from "tech-pkg" to "pkgsrc-users" is that it implies that any user can try to maintain the package (by submitting patches to the mailing list). Since the folks most likely to care about the package are the folks that want to use it or are already using it, this would leverage the energy of users who aren't developers.
2006-03-04 22:28:51 +01:00
MAINTAINER= pkgsrc-users@NetBSD.org
COMMENT should start with a capital letter.
2003-07-21 18:56:41 +02:00
COMMENT= Perl5 module for administration of RFC-2060 IMAP servers
Initial import of p5-IMAP-Admin-1.3.7, a perl module for basic IMAP server administration
2000-10-16 11:11:35 +02:00
This package requires no compiler.
2004-07-23 00:40:16 +02:00
USE_LANGUAGES= # empty
Turn PERL5_PACKLIST into a relative path instead of an absolute path. These paths are now relative to PERL5_PACKLIST_DIR, which currently defaults to ${PERL5_SITEARCH}. There is no change to the binary packages.
2005-07-13 20:01:18 +02:00
PERL5_PACKLIST= auto/IMAP/Admin/.packlist
Initial import of p5-IMAP-Admin-1.3.7, a perl module for basic IMAP server administration
2000-10-16 11:11:35 +02:00
Convert to buildlink2. Use perl5/module.mk. Remove apparently not needed "touch".
2002-10-07 23:11:40 +02:00
.include "../../lang/perl5/module.mk"
Initial import of p5-IMAP-Admin-1.3.7, a perl module for basic IMAP server administration
2000-10-16 11:11:35 +02:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink