pkglint -r --network --only "migrate"
As a side-effect of migrating the homepages, pkglint also fixed a few
indentations in unrelated lines. These and the new homepages have been
checked manually.
Existing SHA1 digests verified, all found to be the same on the
machine holding the existing distfiles (morden). Existing SHA1
digests retained for now as an audit trail.
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
0.80 - 01/16/2006
- Back to libmal again. This version has much better integration with
libmal than 0.43.
There is no functional difference between this version and the last.
0.73 - 12/05/2006
- Several fixes for the pilot-link 0.12 code. Thanks to John McCreesh and
Antoine Jacoutot for their help fixing and testing this.
0.72.2 - 9/12/2006
- Added support for pilot-link 0.12.x
- Updated automake files
0.72.1 - 8/8/2003
- Fixed a bug that caused J-Pilot sync to abort with the cryptic error
message "ReadDBList returned = -1"
0.72 - 7/26/2003
- Upgraded malsync source to malsync 2.1.1
- Updated libmal.c to reflect changes in malsync
- Should now support color devices up to 8bpp (malsync does not yet support
color depths greater than 8bpp)
- Minor changes to malsync source; see the ChangeLog in the malsync
subdirectory for details
- Uses automake. Makefile.am submitted by Ludovic Rousseau
set OVERRIDE_DIRDEPTH to find any libtool scripts deeper in the WRKSRC
tree unless they're named something other than "libtool".
SHLIBTOOL_OVERRIDE generally doesn't need to be specified either -- just
define it to the empty list and shlibtool-override will look for libtool
scripts.
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.
