Age | Commit message (Collapse) | Author | Files | Lines |
|
|
|
|
|
|
|
NetBSD 6, requested by tron.
|
|
Recursively bump package revisions again after the "freetype2" and
"fontconfig" handling was fixed.
|
|
to address issues with NetBSD-6(and earlier)'s fontconfig not being
new enough for pango.
While doing that, also bump freetype2 dependency to current pkgsrc
version.
Suggested by tron in PR 47882
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
a) tiff update to 4.0 (shlib major change)
b) glib2 update 2.30.2 (adds libffi dependency to buildlink3.mk)
Enjoy.
|
|
|
|
|
|
|
|
The changes are fully described at
http://trac.osgeo.org/gdal/wiki/Release/1.8.0-News
However, the following are the highlights.
In a nutshell:
* New GDAL drivers : GTX, HF2, JPEGLS, JP2OpenJPEG, JPIPKAK,
KMLSUPEROVERLAY, LOS/LAS, MG4Lidar, NTv2, OZI, PDF, RASDAMAN,
XYZ
* New OGR drivers : AeronavFAA, ArcObjects, GPSBabel, HTF, LIBKML,
MSSQLSpatial, NAS, OpenAir, PDS, PGDump, SOSI, SUA, WFS
* Significantly improved OGR drivers : DXF, GML
* New implemented RFCs:
o RFC 7: Use VSILFILE for VSI*L Functions
o RFC 24: Progressive data support in GDAL
o RFC 28: OGR SQL Generalized Expressions
o RFC 29: OGR Set Ignored Fields
o RFC 30: Unicode Filenames
o RFC 33: GTIFF - Corrected !PixelIsPoint Interpretation
* New utility : gdallocationinfo
Backward compatibility issues:
* MITAB driver: use "," for the OGR Feature Style id: parameter
delimiter, not "." as per the spec. Known impacted application:
MapServer?
* RFC 33 changes the way PixelIsPoint? is handled for GeoTIFF
* GML driver: write valid <gml:MultiGeometry> element instead of
the non-conformant <gml:GeometryCollection>. For backward
compatibility, recognize both syntax for the reading part
|
|
|
|
"fortran" is alias of "fortran77" for now, but it will change later.
|
|
Also add some patches to remove use of deprecated symbols and fix other
problems when looking for or compiling against libpng-1.4.x.
|
|
|
|
|
|
|
|
|
|
|
|
This changes the buildlink3.mk files to use an include guard for the
recursive include. The use of BUILDLINK_DEPTH, BUILDLINK_DEPENDS,
BUILDLINK_PACKAGES and BUILDLINK_ORDER is handled by a single new
variable BUILDLINK_TREE. Each buildlink3.mk file adds a pair of
enter/exit marker, which can be used to reconstruct the tree and
to determine first level includes. Avoiding := for large variables
(BUILDLINK_ORDER) speeds up parse time as += has linear complexity.
The include guard reduces system time by avoiding reading files over and
over again. For complex packages this reduces both %user and %sys time to
half of the former time.
|
|
Based on PR 39437 by Thomas Zander.
A set of command line tools for reading, writing, manipulating
and viewing high-dynamic range (HDR) images and video frames.
|