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".
_LP64 (which we use), rather than SIZEOF_SIZE_T==8 (which is only defined in
the Debian build goo). Really, the right answer is to add an autoconf test --
or fix the crappy language.
buildlink2.mk files back into the main trunk. This provides sufficient
buildlink2 infrastructure to start merging other packages from the
buildlink2 branch that have already been converted to use the buildlink2
framework.
Remove the --disable-shared option from CONFIGURE_ARGS it doesn't do
anything as pkgsrc libtool isn't built this way. We want shared libraries
anyway...
Use CXX when linking the libraries as we have global contructors that need
calling. Problem only visible on a.out platforms.
pkgsrc. Instead, a new variable PKGREVISION is invented that can get
bumped independent of DISTNAME and PKGNAME.
Example #1:
DISTNAME= foo-X.Y
PKGREVISION= Z
=> PKGNAME= foo-X.YnbZ
Example #2:
DISTNAME= barthing-X.Y
PKGNAME= bar-X.Y
PKGREVISION= Z
=> PKGNAME= bar=X.YnbZ (!)
On subsequent changes, only PKGREVISION needs to be bumped, no more risk
of getting DISTNAME changed accidentally.
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.
version of Federico Lupi's guide by including italian language in
the right file. Hint:
http://lists.oasis-open.org/archives/docbook/200002/msg00214.html
* While there, install the jadetex files not in the textproc/jade
package, but in the print/jadetex package. That's where we also
build and install the jadetex.fmt file, so things actually fit
together.
* Bump some pkg versions:
print/jadetex -> jadetex-2.20nb1
textproc/jade -> jade-1.2.1nb3
meta-pkgs/netbsd-doc -> netbsd-doc-1.2
meta-pkgs/netbsd-doc-print -> netbsd-doc-print-1.1
BUILDLINK_PREFIX.<pkgname>. This allows buildlink to find X11BASE packages
regardless of whether they were installed before or after xpkgwedge was
installed. Idea by Alistair Crooks <agc@pkgsrc.org>.
via buildlink.mk, and mark as USE_BUILDLINK_ONLY. Also disable the -O2
optimization in the package Makefile, instead of removing _all_ the
CXXFLAGS passed to configure. This allows other CXXFLAGS to get through.
Lastly, prefer using a shell loop versus a make loop in the package
Makefile.
