Next | Query returned 42 messages, browsing 21 to 30 | Previous

History of commit frequency

CVS Commit History:


   2005-10-23 21:06:32 by Thomas Klausner | Files touched by this commit (2)
Log message:
Stop using USE_X11BSASE. Bump PKGREVISION.
   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-24 10:52:28 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
Changes 1.2.3:
* Bug fixes
   2005-02-23 18:36:26 by Thomas Klausner | Files touched by this commit (272)
Log message:
Add RMD160 checksums to the SHA1 ones.
   2005-02-21 21:26:15 by Hubert Feyrer | Files touched by this commit (116)
Log message:
Sign over maintainership to tech-pkg@
   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 10:27:56 by Thomas Klausner | Files touched by this commit (3)
Log message:
Unused.
   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-08 04:22:16 by Soren Jacobsen | Files touched by this commit (1)
Log message:
Nuke unnecessary LTCONFIG_OVERRIDE and CONFIGURE_ARGS.

Next | Query returned 42 messages, browsing 21 to 30 | Previous