Next | Query returned 144 messages, browsing 111 to 120 | Previous

History of commit frequency

CVS Commit History:


   2004-07-22 14:38:49 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
Changes 2.0.28:
* Restored support for reading and writing GIF images
* Fix for a possible problem in gdImageTrueColorToPalette
   2004-07-16 09:46:54 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
Changes 2.0.27:
Fixes
* Potential memory overruns in gdImageFilled Polygon
* The sign of Y-axis values returned in the bounding box by gdImageStringFT
   2004-07-01 12:28:42 by Adam Ciarcinski | Files touched by this commit (3)
Log message:
Changes 2.0.26:
* Windows build uses __stdcall calling convention
* Even more complete freetype version checking
* Binary transparency is now handled correctly in gdImageToPalette
   2004-06-20 23:46:36 by Juan Romero Pardines | Files touched by this commit (2)
Log message:
As discussed in tech-pkg, remove X11/Xpm support in graphics/gd.
While I'm here, s/-lpthread/${PTHREAD_LDFLAGS}/.

Bump PKGREVISION.
   2004-05-25 16:55:34 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
Changes 2.0.25:
* Correction in gdfontl.h

Changes 2.0.24:
* bgd.dll is now compatible with Visual BASIC
* Even more complete freetype version checking
* Binary transparency is now handled correctly in gdImageToPalette
   2004-05-09 08:50:30 by Soren Jacobsen | Files touched by this commit (8)
Log message:
No longer used.
   2004-04-26 14:24:13 by Adam Ciarcinski | Files touched by this commit (2)
Log message:
Changes 2.0.23:
* horizontal and vertical DPI hints can now be given to the freetype font
  renderer via the gdFTStringExtra
* several autoconf problems have been addressed
* the current version of freetype is more precisely detected to prevent
  FT_ENCODING_SYMBOL-related errors
* a significant bug in gdNewDynamicCtx was fixed
   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.

Next | Query returned 144 messages, browsing 111 to 120 | Previous