libtool's rules about linking and installing. Worse yet, it encourages
users of the library to reuse its libtool abuse. So we have to whack the
installed .la files to make them correct as if libtool were *correctly*
invoked in the first place.
in the process. (More information on tech-pkg.)
Bump PKGREVISION and BUILDLINK_DEPENDS of all packages using libtool and
installing .la files.
Bump PKGREVISION (only) of all packages depending directly on the above
via a buildlink3 include.
All library names listed by *.la files no longer need to be listed
in the PLIST, e.g., instead of:
lib/libfoo.a
lib/libfoo.la
lib/libfoo.so
lib/libfoo.so.0
lib/libfoo.so.0.1
one simply needs:
lib/libfoo.la
and bsd.pkg.mk will automatically ensure that the additional library
names are listed in the installed package +CONTENTS file.
Also make LIBTOOLIZE_PLIST default to "yes".
all dependencies on packages depending on "png" which contain shared
libraries, all for the (imminent) update to the "png" package.
[List courtesy of John Darrow, courtesy of "bulk-build".]
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
Changes from version 0.13 are a reorganization of the module hierarchy
and three function name changes:
gtk-idle-add-full => gtk-idle-add
gtk-container-foreach-full => gtk-container-foreach
gtk-signal-set-class-function-full => gtk-signal-set-class-function
on graphics/gdk-pixbuf as well since it will build bindings for that if you
have it installed. Based on patches from Jerry Alexandratos
<alexandr@eecis.udel.edu>.
