2004-10-03 02:18:40 by Todd Vierling | Files touched by this commit (863) |
Log message:
Libtool fix for PR pkg/26633, and other issues. Update libtool to 1.5.10
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.
|
2004-09-22 10:10:08 by Johnny C. Lam | Files touched by this commit (703) |
Log message:
Mechanical changes to package PLISTs to make use of LIBTOOLIZE_PLIST.
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".
|
2004-05-05 04:26:42 by Soren Jacobsen | Files touched by this commit (17) |
Log message:
Convert to buildlink3.
|
2004-04-25 00:46:14 by Johnny C. Lam | Files touched by this commit (109) |
Log message:
Relinquish maintainership of packages to tech-pkg@NetBSD.org.
|
2004-01-24 15:58:00 by grant beattie | Files touched by this commit (22) |
Log message:
replace deprecated USE_GMAKE with USE_GNU_TOOLS+=make.
|
2003-07-21 19:16:35 by Martti Kuparinen | Files touched by this commit (31) |
Log message:
COMMENT should start with a capital letter.
|
2003-07-18 00:57:07 by grant beattie | Files touched by this commit (1065) |
Log message:
s/netbsd.org/NetBSD.org/
|
2002-09-11 20:40:12 by Johnny C. Lam | Files touched by this commit (1) |
Log message:
Add a buildlink2.mk file for other package Makefiles.
|
2002-09-11 20:37:11 by Johnny C. Lam | Files touched by this commit (5) | |
Log message:
Initial import of ijs-0.34.
IJS is a client-server protocol for transmission of raster page images.
This package provides a reference implementation of the protocol, the
design of which is still in flux. When the protocol specification is
published, it will be authoritative. Applications should feel free to
link against the library provided in this package, adapt that code for
their own needs, or roll a completely new implementation.
|