Navigation:
Browse pkgsrc
(this page)| 2005-05-22 22:08:52 by Johnny C. Lam | Files touched by this commit (1035) |
Log message: Remove USE_GNU_TOOLS and replace with the correct USE_TOOLS definitions: USE_GNU_TOOLS -> USE_TOOLS awk -> gawk m4 -> gm4 make -> gmake sed -> gsed yacc -> bison |
| 2005-04-11 23:48:17 by Todd Vierling | Files touched by this commit (3539) |
Log message: Remove USE_BUILDLINK3 and NO_BUILDLINK; these are no longer used. |
| 2005-03-03 08:51:40 by grant beattie | Files touched by this commit (2) |
Log message: don't attempt to statically link system libraries. from Eric Boutilier in PR pkg/29470. |
| 2005-02-23 23:24:35 by Alistair G. Crooks | Files touched by this commit (505) |
Log message: Add RMD160 digests. |
| 2004-10-03 02:13:34 by Todd Vierling | Files touched by this commit (908) |
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-03-18 10:12:18 by Johnny C. Lam | Files touched by this commit (232) |
Log message: Fix serious bug where BUILDLINK_PACKAGES wasn't being ordered properly by moving the inclusion of buildlink3.mk files outside of the protected region. This bug would be seen by users that have set PREFER_PKGSRC or PREFER_NATIVE to non-default values. BUILDLINK_PACKAGES should be ordered so that for any package in the list, that package doesn't depend on any packages to the left of it in the list. This ordering property is used to check for builtin packages in the correct order. The problem was that including a buildlink3.mk file for <pkg> correctly ensured that <pkg> was removed from BUILDLINK_PACKAGES and appended to the end. However, since the inclusion of any other buildlink3.mk files within that buildlink3.mk was in a region that was protected against multiple inclusion, those dependencies weren't also moved to the end of BUILDLINK_PACKAGES. |
| 2004-03-05 20:25:43 by Johnny C. Lam | Files touched by this commit (256) |
Log message: Reorder location and setting of BUILDLINK_PACKAGES to match template buildlink3.mk file in revision 1.101 of bsd.buildlink3.mk. |
| 2004-02-14 18:21:56 by Johnny C. Lam | Files touched by this commit (400) |
Log message:
LIBTOOL_OVERRIDE and SHLIBTOOL_OVERRIDE are now lists of shell globs
relative to ${WRKSRC}. Remove redundant LIBTOOL_OVERRIDE settings that
are automatically handled by the default setting in bsd.pkg.mk.
|
| 2004-01-24 04:26:48 by Johnny C. Lam | Files touched by this commit (57) |
Log message: Append to BUILDLINK_DEPENDS.<pkg> instead of setting a default value. In the normal case when BUILDLINK_DEPENDS.<pkg> isn't specified, it receives a value only once due to the multiple inclusion protection in the bulldlink3.mk files. In the case where a package includes several buildlink3.mk files that each want a slightly different version of another dependency, having BUILDLINK_DEPENDS.<pkg> be a list allows for the strictest <pkg> dependency to be matched. |
New packages: