summaryrefslogtreecommitdiff
path: root/mail/evolution
diff options
context:
space:
mode:
authorjlam <jlam>2004-01-04 20:57:31 +0000
committerjlam <jlam>2004-01-04 20:57:31 +0000
commit73640d83be6707756ee7e26600e9cedb811484f8 (patch)
treeb0ea489f12b84bd8625e9c456aff9742666b877d /mail/evolution
parent37e6d1a0536582d752d8beeb7588b0385eae0f86 (diff)
downloadpkgsrc-73640d83be6707756ee7e26600e9cedb811484f8.tar.gz
BUG FIXES:
* Don't add any dependencies (via BUILDLINK_DEPENDS) unless buildlink3.mk files add them. This fixes case where the software existed both in the base system and in /usr/pkg, we used only the built-in software, but we still recorded a dependency on the one in /usr/pkg. * Re-structure the code that populates ${BUILDLINK_DIR} so that we don't bump into ARG_MAX limits in the shell. This should fix the problem present in the buildlink2 framework noted in: http://mail-index.netbsd.org/tech-pkg/2004/01/03/0005.html CHANGES: * Define a new yes/no variable BUILDLINK_USE_BUILTIN.<pkg> that determines if we should use the built-in software or not. This should probably replace the various USE_NCURSES, USE_GNU_READLINE, USE_GNU_GETTEXT, etc. variables with something whose naming is a bit more consistent and is integrated directly into the buildlink3 framework. * Garbage-collect "$$pkg_prefix", which was used exclusively in BUILDLINK_FILES_CMD.<pkg>. It no longer exists in the buildlink3/pkgviews world. Packages _should_ _no_ _longer_ directly set the PREFIX variable in the package Makefile. As a consequence, the various Java VM packages will need some changes when they're converted to use buildlink3.
Diffstat (limited to 'mail/evolution')
0 files changed, 0 insertions, 0 deletions