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

22 lines
603 B
Makefile
Raw Normal View History

lang/php: reset PKGREVISION Reset PKGREVISION with all php's version updates.
2018-07-20 15:33:02 +02:00
# $NetBSD: Makefile,v 1.28 2018/07/20 13:33:02 taca Exp $
Add PDO (PHP Data Objects) extensions. These implement unified, object-oriented interface to various databases. PDO comes bundled with upcoming PHP 5.1, but can also be used with PHP 5.0 via PECL.
2005-10-09 15:11:18 +02:00
The php_pdo* packages have not kept step with PHP changes. The PDO components are now built into PHP rather than maintained separately in PECL. The old PECL versions are unmaintained and haven't been altered for 3 years. This is confusing as the package versions report themselves to be 5.2.9.1.0.2, etc. but they are in fact based on the 5.1.x code-base. Therefore, we need to switch to building the PDO modules like any other PHP module. A side-effect of this is that the PECL version number will get stripped off the end meaning that the new version numbers are just 5.2.9 instead of 5.2.9.1.0.2 (for example). Unfortunately, 5.2.9 is considered to be older than 5.2.9.1.0.2 meaning that it will appear as though a downgrade has taken place. Therefore, while we are still using PHP 5.2.9, add .99 on the end (i.e. 5.2.9.99) so that the package appears newer. When PHP 5.2.10 is released this can be removed (the module.mk file explicitly cgecks for 5.2.9 before adding the .99 suffix so that it will not alter 5.2.10 if the hack is forgotten. However, for the record, when 5.2.10 is released, php-pdo/module.mk can be removed along with the references to it in each php-pdo*/Makefile
2009-03-13 11:57:20 +01:00
MODNAME= pdo_dblib
CATEGORIES+= databases
COMMENT= PHP extension for PHP Data Objects (FreeTDS/Sybase/MS SQL)
Update the PHP PDO to latest available PECL versions (1.0/1.0.1/1.0.2). Changes are bugfixes mostly. Also rework php-pdo/module.mk somewhat, so that the base php-pdo package can use it too.
2005-12-03 18:24:28 +01:00
The php_pdo* packages have not kept step with PHP changes. The PDO components are now built into PHP rather than maintained separately in PECL. The old PECL versions are unmaintained and haven't been altered for 3 years. This is confusing as the package versions report themselves to be 5.2.9.1.0.2, etc. but they are in fact based on the 5.1.x code-base. Therefore, we need to switch to building the PDO modules like any other PHP module. A side-effect of this is that the PECL version number will get stripped off the end meaning that the new version numbers are just 5.2.9 instead of 5.2.9.1.0.2 (for example). Unfortunately, 5.2.9 is considered to be older than 5.2.9.1.0.2 meaning that it will appear as though a downgrade has taken place. Therefore, while we are still using PHP 5.2.9, add .99 on the end (i.e. 5.2.9.99) so that the package appears newer. When PHP 5.2.10 is released this can be removed (the module.mk file explicitly cgecks for 5.2.9 before adding the .99 suffix so that it will not alter 5.2.10 if the hack is forgotten. However, for the record, when 5.2.10 is released, php-pdo/module.mk can be removed along with the references to it in each php-pdo*/Makefile
2009-03-13 11:57:20 +01:00
USE_PHP_EXT_PATCHES= yes
.include "../../mk/bsd.prefs.mk"
.include "../../lang/php/ext.mk"
Add PDO (PHP Data Objects) extensions. These implement unified, object-oriented interface to various databases. PDO comes bundled with upcoming PHP 5.1, but can also be used with PHP 5.0 via PECL.
2005-10-09 15:11:18 +02:00
The php_pdo* packages have not kept step with PHP changes. The PDO components are now built into PHP rather than maintained separately in PECL. The old PECL versions are unmaintained and haven't been altered for 3 years. This is confusing as the package versions report themselves to be 5.2.9.1.0.2, etc. but they are in fact based on the 5.1.x code-base. Therefore, we need to switch to building the PDO modules like any other PHP module. A side-effect of this is that the PECL version number will get stripped off the end meaning that the new version numbers are just 5.2.9 instead of 5.2.9.1.0.2 (for example). Unfortunately, 5.2.9 is considered to be older than 5.2.9.1.0.2 meaning that it will appear as though a downgrade has taken place. Therefore, while we are still using PHP 5.2.9, add .99 on the end (i.e. 5.2.9.99) so that the package appears newer. When PHP 5.2.10 is released this can be removed (the module.mk file explicitly cgecks for 5.2.9 before adding the .99 suffix so that it will not alter 5.2.10 if the hack is forgotten. However, for the record, when 5.2.10 is released, php-pdo/module.mk can be removed along with the references to it in each php-pdo*/Makefile
2009-03-13 11:57:20 +01:00
CONFIGURE_ARGS+= --with-${MODNAME}
For a configure argument, remove freetds subdirectory since my recent freetds package changes. Didn't bump PKGREVISION. The resulting library doesn't appear to reference freetds location.
2006-01-04 18:59:14 +01:00
CONFIGURE_ARGS+= --with-${PKGMODNAME}=shared,${BUILDLINK_DIR}
Add PDO (PHP Data Objects) extensions. These implement unified, object-oriented interface to various databases. PDO comes bundled with upcoming PHP 5.1, but can also be used with PHP 5.0 via PECL.
2005-10-09 15:11:18 +02:00
# requires 0.63 version to compile, doesn't compile with 0.61
Over 1200 files touched but no revisions bumped :) RECOMMENDED is removed. It becomes ABI_DEPENDS. BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo. BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo. BUILDLINK_DEPENDS does not change. IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS which defaults to "yes". Added to obsolete.mk checking for IGNORE_RECOMMENDED. I did not manually go through and fix any aesthetic tab/spacing issues. I have tested the above patch on DragonFly building and packaging subversion and pkglint and their many dependencies. I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I have used IGNORE_RECOMMENDED for a long time). I have been an active user of IGNORE_RECOMMENDED since it was available. As suggested, I removed the documentation sentences suggesting bumping for "security" issues. As discussed on tech-pkg. I will commit to revbump, pkglint, pkg_install, createbuildlink separately. Note that if you use wip, it will fail! I will commit to pkgsrc-wip later (within day).
2006-04-06 08:21:32 +02:00
BUILDLINK_API_DEPENDS.freetds+= freetds>=0.63
Add PDO (PHP Data Objects) extensions. These implement unified, object-oriented interface to various databases. PDO comes bundled with upcoming PHP 5.1, but can also be used with PHP 5.0 via PECL.
2005-10-09 15:11:18 +02:00
.include "../../databases/freetds/buildlink3.mk"
Update the PHP PDO to latest available PECL versions (1.0/1.0.1/1.0.2). Changes are bugfixes mostly. Also rework php-pdo/module.mk somewhat, so that the base php-pdo package can use it too.
2005-12-03 18:24:28 +01:00
.include "../../databases/php-pdo/buildlink3.mk"
Don't abuse b3. It should not do things like include bsd.pkg.mk, so fix up the packages that use it instead.
2009-03-05 21:58:37 +01:00
.include "../../mk/bsd.pkg.mk"
Reference in a new issue Copy permalink