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.
Do it for all packages that
* mention perl, or
* have a directory name starting with p5-*, or
* depend on a package starting with p5-
like last time, for 5.18, where this didn't lead to complaints.
Let me know if you have any this time.
are replaced with .include "../../devel/readline/buildlink3.mk", and
USE_GNU_READLINE are removed,
* .include "../../devel/readline/buildlink3.mk" without USE_GNU_READLINE
are replaced with .include "../../mk/readline.buildlink3.mk".
a) refer 'perl' in their Makefile, or
b) have a directory name of p5-*, or
c) have any dependency on any p5-* package
Like last time, where this caused no complaints.
This is to get 0.12.5 out with the new Calendar code so J-Pilot
can get their release out. I will be dropping a 0.12.5.1 release
shortly after this with the patches rolled up from 0.12.4 to current
pushed in.
Last-minute fixes before releasing 0.12.4
Fix for Sony SJ-22 device sync (fixes bug #1957 filed at
bugs.pilot-link.org)
Updated documentation to reflect a cleaner layout and output
(closes bug #1913 in the bugtracker at bugs.pilot-link.org
Integrate jpilot's contacts support. See
http://lists.pilot-link.org/pipermail/pilot-link-devel/2009-February/001762.html
Adding CalendarDB support to pilot-link
Adding minor tweak for m4 macro optimizations
Minor fix for a buffer size miscalculation (from Nicholas Piper)
Adding missing newline at the end of the file.
pi-debug.h, pi-threadsafe.h: Cleaning up unnecessary references
to config.h here.
Added pi-md5.h.in
generates pi-md5.h
Now autogenerated from pi-md5.h.in
Add minor fix for reported segfault when closing down bluetooth
connection. This closes bug #1872
UINT32 was broken on 64-bit systems. This should fix it on most
systems.
Increment ChangeLog to test/validate an LDAP permission issue
with LockDir
Implementing a Zire 22 fix from Tom Billiet
Bump for 0.12.4
Added Aaron's fixes (oof! This has been in the queue for awhile.
Sorry Aaron). This closes bug #1448.
--------------------------------------------------------------------------
pilot-link 0.12.3, "Can-of-Raid" (aka "Bug-Squash" release), 11-12-2007
--------------------------------------------------------------------------
Here you go, another pilot-link release. This one fixes quite a few issues:
Bug Fixes:
* Fix for Sony NR70 devices not being detected properly
* BlueZ detection fix
* XSLT manpage autogeneration fixes
* Perl bindings build error, remove autoconfiscated files from
releases
* Java bindings build errors, remove autoconfiscated Makefile
* Renamed pilot-treofoto and pilot-650foto to pilot-foto-treo600 and
pilot-foto-treo650
* Added missing manpages for pilot-foto-treo6xx
* Fixed OS5 failures with pilot-addresses.c
* Updated pilot-install-memo.c to allow installation of files
outside the current working directory
* Fix for pi_usb_accept, adding PI_ERR_SOCK_LISTENER from Matt
Davey's patch (closing #1782)
Check the ChangeLog for the details on all fixes for this release
--------------------------------------------------------------------------
pilot-link 0.12.2, "Dance With the Devil" aka "Distraction", 02-09-2007
--------------------------------------------------------------------------
5 months since the last release (0.12.1) and we have another release! This
one is mostly a maintenance release, but there are some new things in here.
Major Features:
* More cleanup in libpisock and documentation, addition of some new
(working :) BlueZ support, new udev rules, expanded OS5 Contacts
support, expanded OS X support and a lot more!
Other Features:
* No major features in this release, mostly bug fixes and minor
tweaks here and there. The website has also been refreshed with
new content and a completely new layout. All source files are now
version-tracked in the header.
Bug Fixes:
* Python support was broken, fixed now, doh! Palm T|X over libusb
has been fixed (we hope) with this release. Of course we need
testers to validate that. All of userland is renamed now to avoid
some namespace pollution. Documentation is all current with
respect to this release, all manpages are in XML source format
(requires xsltproc to process), and much more.
pilot-link v0.12.1
There isn't much "new" in this release, just some rapid-fire bug fixes
reported from users and a lot of code has been cleaned up in the tree
to remove unnecessary includes.
* Code cleanup in libpisock, libpisync, src and include
* Fixed the installation faux pas with udev rules, oops!
pilot-link v0.12.0
pilot-link 0.12.0 "Trois ans" ("Three Years") is now official.
There have been so many changes in this release and I can't remember
them all, but here's the short list:
* Many of the userland binaries now have new names, to avoid some
potential namespace collisions (dlpsh is now pilot-dlpsh for example,
memos is now pilot-memos). If you use scripts which call these
applications, you may have to make minor changes to accomodate the
new naming scheme.
* Documentation is now in DocBook XML, and manpages are dynamically
generated from that source. Other docs are much more detailed, and
there are quite a few README files that have been added to help.
* Direct libusb support! This is one of the most monumental features in
0.12.0, and should help those who have trouble using the kernel's
visor driver in Linux with their device. Now you can get a healthy
300% to 600% speedup in sync times, depending on your Palm's
processor speed. See doc/README.libusb for details. Thanks go to
Zephania Hull for working out how to get native libusb working with
pilot-link.
* Native support for Mac OS X. You can now just download the tarball
and build it directly on Mac OS X machines, and it will just run.
Thanks go to Florent Pillet for his tireless work in getting this all
working efficiently and for squashing countless bugs in the libraries
along the way.
* So many other fixes, additions, features and new things to count.
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).
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.
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.
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.
