The find-prefix infrastructure was required in a pkgviews world where
packages installed from pkgsrc could have different installation
prefixes, and this was a way for a dependency prefix to be determined.
Now that pkgviews has been removed there is no longer any need for the
overhead of this infrastructure. Instead we use BUILDLINK_PREFIX.pkg
for dependencies pulled in via buildlink, or LOCALBASE/PREFIX where the
dependency is coming from pkgsrc.
Provides a reasonable performance win due to the reduction of `pkg_info
-qp` calls, some of which were redundant anyway as they were duplicating
the same information provided by BUILDLINK_PREFIX.pkg.
When a package depends on mysql-client, in includes mk/mysql-buildlink3.mk
and may get buildlinked with mariadb55-client if MYSQL_VERSION_DEFAULT is
set to MARIADB55.
mariadb55-client's buildlink3.mk defined BUILDLINK_*.mariadb-client
variables, wich caused build problems with packages expecting
BUILDLINK_*.mysql-client to be defined. For instance, php-pdo_mysql
expectex BUILDLINK_PREFIX.mysql-client to be set and fails to build
without it.
Fix the problem by changing BUILDLINK_*.mariadb-client to
BUILDLINK_*.mysql-client in mariadb55-client/buildlink3.mk. Remove a
package specific woakrround for this exact ptoblem in php-mysqli.
NB: commit log on pkgsrc/databases/mariadb55-client/buildlink3.mk 1.2-1.3
and pkgsrc/databases/php-mysqli/Makefile 1.12-1.13 was truncated. This
change just adds a comment to the first file and a null-commit to the
second file to have an oportunity to provide the full cvs log.
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@.
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.
