Next | Query returned 67 messages, browsing 31 to 40 | Previous

History of commit frequency

CVS Commit History:


   2004-12-24 09:04:26 by Jeremy C. Reed | Files touched by this commit (2)
Log message:
Bump PKGREVISION and also bump the BUILDLINK_RECOMMENDED.libglade2
to latest, because it was never bumped before when one of its
NEEDED shared libraries was upgraded.
   2004-12-24 01:09:06 by Jeremy C. Reed | Files touched by this commit (1)
Log message:
Add a BUILDLINK_RECOMMENDED.libglade2 for at least 2.3.6nb1.
The BUILD_DEPENDS dates back to September and so
libglade shared libraries from then need old (no longer existing)
libxml, pango, and gtk2 libraries.

I noticed this when installing packages on a machine that already had
the (what it thought was) correct dependencies.
   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-09-02 14:14:29 by Julio M. Merino Vidal | Files touched by this commit (3)
Log message:
Update to 2.4.0: the code has been marked as stable and some cleanups have
been done.
   2004-05-03 23:19:03 by Soren Jacobsen | Files touched by this commit (1)
Log message:
No longer used.
   2004-04-20 18:14:03 by Julio M. Merino Vidal | Files touched by this commit (1)
Log message:
Handle the lib/libglade and lib/libglade/2.0 directories properly during
print-PLIST.
   2004-04-17 12:39:23 by Julio M. Merino Vidal | Files touched by this commit (1)
Log message:
Require glib2 >= 2.4.0nb2 to get the dlopen(NULL, 0) workaround, because
this functionality is used by this library.  Bump PKGREVISION to 1.
   2004-04-01 20:16:46 by Julio M. Merino Vidal | Files touched by this commit (7)
Log message:
Update to 2.3.6:

libglade-2.3.6: 10-March-2004
- Implement support GtkComboBoxEntry, GtkToolItem, GtkToolButton,
  GtkToggleToolButton, GtkRadioToolButton & GtkSeparatorToolItem (Damon
  Chaplin)
- Fix automake warning (Steve Chaplin)
- Add libglade version number to the docs (Matthias Clasen)
- Fix usage of C++ keyword as an argument name (Bas Driessen)
- Allow additional signal parameter for glademm (Christof Petig)
- Support tooltips in toolbars (Michael Voigt)

libglade-2.3.2: 15-January-2004
- Support disambiguating msgids by prefixing them with a context
  string. (Christian Stimming, Matthias Clasen)

libglade-2.3.1:  14-November-2003
- Register GtkColorButton, GtkComboBox, GtkFileChooser and
  GtkFontButton types (Jonathan Blandford)
- Implemement support for GtkExpander (Mark McLoughlin)
- Fix memory leak and incorrect colour map usage (Morten Welinder)
- Win32 build support (Tor Lillqvist, Masahiro Sakai)
- Build fixes (James Henstridge, Michael Meeks)
   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.

Next | Query returned 67 messages, browsing 31 to 40 | Previous