kpriv/pkgsrc
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity
pkgsrc/mail/php-imap/Makefile

28 lines
880 B
Makefile
Raw Normal View History

Fix CONFLICTS of php/pear packages, the asterix was missing (thanks tv). While going through the tree, fix some more packages which had similiar issues with too strict conflicts, bump the revisions of those.
2006-06-04 18:26:54 +02:00
# $NetBSD: Makefile,v 1.11 2006/06/04 16:26:54 joerg Exp $
new PHP extension module framework, which makes it possible to build individual PHP extension packages with either PHP 4.x or PHP 5.x convert existing php4-* packages to this framework and import as php-*
2004-10-31 20:30:29 +01:00
MODNAME= imap
CATEGORIES+= mail
COMMENT= PHP extension for IMAP (Internet Mailbox Access Protocol)
Fix CONFLICTS of php/pear packages, the asterix was missing (thanks tv). While going through the tree, fix some more packages which had similiar issues with too strict conflicts, bump the revisions of those.
2006-06-04 18:26:54 +02:00
CONFLICTS= php-imap-[0-9]*
Rename all PHP 4 packages to php4-*, all PHP 5 packages to php5-*, all PEAR packages to php?-pear-* and all Apache packages to ap13-* or ap2-* respectively. Add new variables to simplify the Makefile handling. Add CONFLICTS on the old names. Reset revisions of bumped packages. ap-php will now depend on the default Apache and PHP version. All programs using it have an implicit option of the Apache version as well. OK from jlam@ and adrianp@.
2006-06-02 20:27:54 +02:00
new PHP extension module framework, which makes it possible to build individual PHP extension packages with either PHP 4.x or PHP 5.x convert existing php4-* packages to this framework and import as php-*
2004-10-31 20:30:29 +01:00
USE_PHP_EXT_PATCHES= yes
CONFIGURE_ARGS+= --with-${MODNAME}=shared,${BUILDLINK_PREFIX.imap-uw}
CONFIGURE_ARGS+= --with-${MODNAME}-ssl=${SSLBASE}
CONFIGURE_ARGS+= --with-${MODNAME}-linkage
g/c LIBS setting
2005-04-16 09:37:30 +02:00
new PHP extension module framework, which makes it possible to build individual PHP extension packages with either PHP 4.x or PHP 5.x convert existing php4-* packages to this framework and import as php-*
2004-10-31 20:30:29 +01:00
CONFIGURE_ENV+= ac_cv_lib_pam_pam_start=no
Explain setting PHP_OPENSSL (from Stoned Elipot)
2005-04-20 14:03:25 +02:00
# Imap extension's config.m4 calls m4 macro PHP_SETUP_OPENSSL() which
# expects PHP_ARG_WITH(openssl, ...) being called beforehand so that
# PHP_OPENSSL is set. For a self contained extension build like for
# this package this is not the case of course.
Fixed pkglint warnings. The warnings are mostly quoting issues, for example MAKE_ENV+=FOO=${BAR} is changed to MAKE_ENV+=FOO=${BAR:Q}. Some other changes are outlined in http://mail-index.netbsd.org/tech-pkg/2005/12/02/0034.html
2005-12-05 21:49:47 +01:00
CONFIGURE_ENV+= PHP_OPENSSL=${SSLBASE:Q}
new PHP extension module framework, which makes it possible to build individual PHP extension packages with either PHP 4.x or PHP 5.x convert existing php4-* packages to this framework and import as php-*
2004-10-31 20:30:29 +01:00
.include "../../mail/imap-uw/buildlink3.mk"
.include "../../security/openssl/buildlink3.mk"
now that PHP 5.x Makefile.common doesn't pollute CONFIGURE_ARGS, it safe to include "../../lang/php/ext.mk" after extension CONFIGURE_ARGS setting; successful build confirmed with both PHP 4.x and PHP 5.x
2004-11-05 18:11:39 +01:00
.include "../../lang/php/ext.mk"
new PHP extension module framework, which makes it possible to build individual PHP extension packages with either PHP 4.x or PHP 5.x convert existing php4-* packages to this framework and import as php-*
2004-10-31 20:30:29 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink