Installed docs changed a bit.
upstream changes:
- Fixed support for PostgreSQL 8.2
- Fixed bug in collect() function discarding SRID of input
- Added SRID match check in MakeBox2d and MakeBox3d
- Fixed regress tests to pass with GEOS-3.0.0
- Improved pgsql2shp run concurrency.
- [many java changes]
object-relational database. In effect, PostGIS "spatially enables" the
PostgreSQL server, allowing it to be used as a backend spatial
database for geographic information systems (GIS), much like ESRI's
SDE or Oracle's Spatial extension. PostGIS follows the OpenGIS "Simple
Features Specification for SQL" and has been certified as compliant
with the "Types and Functions" profile. PostGIS/PostgreSQL includes
the following functionality:
* Simple Features as defined by the OpenGIS Consortium (OGC)
* Support for Well-Known Text and Well-Known Binary
representations of GIS objects
* Fast spatial indexing using GiST
* Geospatial analysis functions
* PostgreSQL JDBC extension objects corresponding to the
geometries
* Support for OGC access functions as defined by the Simple
Features Specification
Based on package in pkgsrc-wip by mchittur@cs.nmsu.edu. Updated to
not require building in PG source dir now that postgresql81-client
installs the "server" include fies.
* Fri Jun 9 2006 Eric S. Raymond <esr@snark.thyrsus.com> - 2.33-1
- Fix bad unit conversion in V output. Clean up some man-page messes.
Fixed buggy libgps parsing of multiple responses. It's now possible
to lock gpsd to a fixed speed at compile time for embedded use. Added
NTRIP support, thanks to Ville Nuorvala. O command now ships an
explicit mode field.
* Sun Mar 12 2006 Eric S. Raymond <esr@snark.thyrsus.com> - 2.32-1
- Cleanup of the xgps layout, and minor memory-leak fixes for xgps. Fix
to cope with Antares uBlox by Andreas Stricker. Minor fix to libgps
cgpxlogger. Merge cgpxlogger and gpxlogger documentation onto
the xgps(1) manual page and rename it gps(1).
since they always need a C compiler, even when the source code is
completely in C++.
For some other packages, stated in the comment that a C compiler is
really not needed.
and add a new helper target and script, "show-buildlink3", that outputs
a listing of the buildlink3.mk files included as well as the depth at
which they are included.
For example, "make show-buildlink3" in fonts/Xft2 displays:
zlib
fontconfig
iconv
zlib
freetype2
expat
freetype2
Xrender
renderproto
Mahesh Chittur, and Brook Milligan in pkgsrc-wip.
GDAL is a translator library for raster geospatial data formats that
is released under an X/MIT style Open Source license. As a library, it
presents a single abstract data model to the calling application for
all supported formats. The related OGR library (which lives within
the GDAL source tree) provides a similar capability for simple
features vector data. It includes roughly 60 format drivers. Current
translators include:
* GeoTIFF (read/write)
* Erdas Imagine (read/write)
* ESRI .BIL (read)
* .aux labelled raw (read/write)
* DTED (read)
* SDTS DEM (read)
* CEOS (read)
* JPEG (read/write)
* PNG (read/write)
* Geosoft GXF (read)
* Arc/Info Binary Grid (read)
A full list is available at
http://www.remotesensing.org/gdal/formats_list.html
PKGLOCALEDIR and which install their locale files directly under
${PREFIX}/${PKGLOCALEDIR} and sort the PLIST file entries. From now
on, pkgsrc/mk/plist/plist-locale.awk will automatically handle
transforming the PLIST to refer to the correct locale directory.
RECOMMENDED is removed. It becomes ABI_DEPENDS.
BUILDLINK_RECOMMENDED.foo becomes BUILDLINK_ABI_DEPENDS.foo.
BUILDLINK_DEPENDS.foo becomes BUILDLINK_API_DEPENDS.foo.
BUILDLINK_DEPENDS does not change.
IGNORE_RECOMMENDED (which defaulted to "no") becomes USE_ABI_DEPENDS
which defaults to "yes".
Added to obsolete.mk checking for IGNORE_RECOMMENDED.
I did not manually go through and fix any aesthetic tab/spacing issues.
I have tested the above patch on DragonFly building and packaging
subversion and pkglint and their many dependencies.
I have also tested USE_ABI_DEPENDS=no on my NetBSD workstation (where I
have used IGNORE_RECOMMENDED for a long time). I have been an active user
of IGNORE_RECOMMENDED since it was available.
As suggested, I removed the documentation sentences suggesting bumping for
"security" issues.
As discussed on tech-pkg.
I will commit to revbump, pkglint, pkg_install, createbuildlink separately.
Note that if you use wip, it will fail! I will commit to pkgsrc-wip
later (within day).
without underscores (REPLACE.*.old, REPLACE.*.new, and REPLACE_FILES.*).
Also convert REPLACE.*.new= ${SH:Q} back to ${SH}, as it should not be quoted
here, if at all.
Ok with rillig.
developer is officially maintaining the package.
The rationale for changing this from "tech-pkg" to "pkgsrc-users" is
that it implies that any user can try to maintain the package (by
submitting patches to the mailing list). Since the folks most likely
to care about the package are the folks that want to use it or are
already using it, this would leverage the energy of users who aren't
developers.
this is a major upgrade (from 1.07), please check the homepage for
details
(I've played with 2.30 for a while and it worked well.)
closes PR pkg/32872 by Evan Hall; thanks for the ncurses hint, wouldn't
have found it myself
GEOS (Geometry Engine - Open Source) is a C++ port of the Java
Topology Suite (JTS). It contain the complete functionality of JTS in
C++. It includes all the OpenGIS "Simple Features for SQL" spatial
predicate functions and spatial operators,and JTS topology functions
like IsValid().
Several changes are involved since they are all interrelated. These
changes affect about 1000 files.
The first major change is rewriting bsd.builtin.mk as well as all of
the builtin.mk files to follow the new example in bsd.builtin.mk.
The loop to include all of the builtin.mk files needed by the package
is moved from bsd.builtin.mk and into bsd.buildlink3.mk. bsd.builtin.mk
is now included by each of the individual builtin.mk files and provides
some common logic for all of the builtin.mk files. Currently, this
includes the computation for whether the native or pkgsrc version of
the package is preferred. This causes USE_BUILTIN.* to be correctly
set when one builtin.mk file includes another.
The second major change is teach the builtin.mk files to consider
files under ${LOCALBASE} to be from pkgsrc-controlled packages. Most
of the builtin.mk files test for the presence of built-in software by
checking for the existence of certain files, e.g. <pthread.h>, and we
now assume that if that file is under ${LOCALBASE}, then it must be
from pkgsrc. This modification is a nod toward LOCALBASE=/usr. The
exceptions to this new check are the X11 distribution packages, which
are handled specially as noted below.
The third major change is providing builtin.mk and version.mk files
for each of the X11 distribution packages in pkgsrc. The builtin.mk
file can detect whether the native X11 distribution is the same as
the one provided by pkgsrc, and the version.mk file computes the
version of the X11 distribution package, whether it's built-in or not.
The fourth major change is that the buildlink3.mk files for X11 packages
that install parts which are part of X11 distribution packages, e.g.
Xpm, Xcursor, etc., now use imake to query the X11 distribution for
whether the software is already provided by the X11 distribution.
This is more accurate than grepping for a symbol name in the imake
config files. Using imake required sprinkling various builtin-imake.mk
helper files into pkgsrc directories. These files are used as input
to imake since imake can't use stdin for that purpose.
The fifth major change is in how packages note that they use X11.
Instead of setting USE_X11, package Makefiles should now include
x11.buildlink3.mk instead. This causes the X11 package buildlink3
and builtin logic to be executed at the correct place for buildlink3.mk
and builtin.mk files that previously set USE_X11, and fixes packages
that relied on buildlink3.mk files to implicitly note that X11 is
needed. Package buildlink3.mk should also include x11.buildlink3.mk
when linking against the package libraries requires also linking
against the X11 libraries. Where it was obvious, redundant inclusions
of x11.buildlink3.mk have been removed.
Price:
The Shapefile C Library provides the ability to write simple C programs
for reading, writing and updating (to a limited extent) ESRI
Shapefiles, and the associated attribute file (.dbf). The Shapefile
format is a working and interchange format promulgated by ESRI for
simple vector data with attributes.
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.
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".
brook at biology dot nmsu dot edu and his team at NMSU.
MapServer is an OpenSource development environment for building spatially
enabled Internet applications. It now supports MapScript which allows popular
scripting languages such as Perl, Python, Tk/Tcl, Guile and even Java to
access the MapServer C API. MapScript provides a rich environment for
developing applications that integrate disparate data.
brook at biology dot nmsu dot edu and his team at NMSU.
Vis5D is a system for interactive visualization of large 5-D gridded data sets
such as those produced by numerical weather models. One can make isosurfaces,
contour line slices, colored slices, volume renderings, etc of data in a 3-D
grid, then rotate and animate the images in real time. There is also a feature
for wind trajectory tracing, a way to make text anotations for publications,
support for interactive data analysis, etc. GRASS can import and export Vis5D
raster data.
brook at biology dot nmsu dot edu and his team at NMSU.
The gpsutils package covers some small applications to capture and convert
data from a Garmin GPS receiver. These are based on a included more general
GPS library (in C).
Initial import of gpspoint, one of the many packages provided by
brook at biology dot nmsu dot edu and his team at NMSU.
This package provides a program and library to download and upload waypoints,
routes, and tracks to and from your GPS device. Upload and download is
possible via the GARMIN interface. Current position obtainable via the NMEA
Interface, supported by most GPS devices.
