Next | Query returned 128 messages, browsing 101 to 110 | Previous

History of commit frequency

CVS Commit History:


   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-15 23:12:45 by Soren Jacobsen | Files touched by this commit (1)
Log message:
No longer used.
   2004-05-09 12:12:08 by Marc Recht | Files touched by this commit (2)
Log message:
after jmmv's glib2 fixes patch-aa isn't needed anymore
   2004-04-15 02:49:29 by Thomas Klausner | Files touched by this commit (13)
Log message:
The buildlink2 framework does nothing with .pc files -- remove them
from the buildlink2.mk files.
   2004-04-14 18:15:30 by Julio M. Merino Vidal | Files touched by this commit (147)
Log message:
Make use of the new USE_DIRS variable, instead of directly depending on the
*-dirs packages.
   2004-04-05 15:27:00 by Matthias Scheler | Files touched by this commit (2)
Log message:
Add conflicts with each other to the "gtk-engines" and the \ 
"gtk2-engines"
package because they installed identical files into the same directory.
   2004-04-05 00:44:06 by Marc Recht | Files touched by this commit (3)
Log message:
Fix a problem with the "redmond" engine which was missing the gtk2 symbols.
Bump the PKGREVISION to 7 for this change.
   2004-04-01 21:02:34 by Julio M. Merino Vidal | Files touched by this commit (4) | Package updated
Log message:
Bump PKGREVISION to 6 and fix paths to installed files, due to the update
of GTK+ to 2.4.
   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.

Next | Query returned 128 messages, browsing 101 to 110 | Previous