Changes from v1.108 to v1.109
* Conduits included in the PilotManager distribution now have
version numbers identical to the PilotManager version.
Third-party conduits can (and should) continue to have their own
version number schemes.
* Change the way we reference constants exported from libpisock,
in preparation for pilot-link 0.12.0-pre5. Backwards
compatibility is maintained. Use symbolic constants instead of
hard-coded integer values, if running with a version of pilot-link
that provides them.
* A second attempt to fix the bug in the Properties dialog with
Tk-804. The first one didn't work with certain combinations of
libraries.
* Fix bug introduced in 1.108 that broke -syncwith and -install
for normally inactive conduits.
* Don't call conduitQuit on conduits that haven't been loaded.
Eliminates an error message when using -syncwith (bug introduced
in 1.108).
* Fix bug where PilotManager would report a successful connection
and then a Perl error, when what really happened was simply a
timeout.
* Eliminated numerous -w warnings
* PilotSync.pm (affects SyncAB, SyncFood, and some third-party
conduits; all changes by Ralf Schlatterbeck): fix some crash bugs
and a bug that caused creation of empty fields; add support for
full sync; some new functionality for use by conduit authors:
possibility to skip some pilot records, and to generate local ID
based on contents of pilot record.
* SyncMemo conduit: work around a bug in perl 5.8.0 that was
causing the filename filters not to work sometimes. The
workaround involves forcing these filters to be ASCII-only; this
could conceivably be a problem for people using non-ASCII
filenames. Fix bug that caused spurious conflict to be detected
when doing full sync and a file had changed but the corresponding
pilot memo had not. Eliminate some barewords to avoid strict subs
warnings in some versions of perl (bug report from Ralf
Schlatterbeck).
* SyncCM conduit: Work around libcsa bug that was causing "INVALID
DATE TIME" error when syncing "all dates" in a timezone east of
GMT; workaround for dtcm bug that made weekly repeating
appointments created on the pilot uneditable in dtcm; fix up
repeating appointments from the pilot whose start date isn't one
of the repeat days. The following patches from Alan Harder: if cm
appointment has no end time, use end time equal to start time on
pilot (rather than refusing to sync the appointment); clearer and
more informative log messages; when doing "Sync All (dates)", use
2021 instead of 2010 as the end of the range; propagate
appointment deletion from palm to desktop even if the archive flag
is set.
* Installer conduit: Respect -rcdir argument when running
installer from command line (Alan Harder)
* Backup conduit: add an option "Ignore modify date (backup every
time)"; more informative log messages. (Both by Alan Harder.)
For deciding whether to back up a database, use a different scheme
that doesn't depend on the two clocks being synchronized.
* SyncTime conduit: remove workaround for some ancient pilot-link
version (Alan Harder).
* SyncFood conduit: Refuse to sync if $FOODFILE has been deleted,
in order to avoid wiping everything out. Patch from Alan Harder, I
haven't tested it.
* SyncAB conduit: fix bug in setting vCard file name, and in
handling of newlines (Alan Harder). Implement full sync, allowing
sync with multiple desktop machines (Ralf Schlatterbeck). Allow
filtering by private flag and by category (Ralf Schlatterbeck).
* SyncPlan conduit: Appointments that repeat more than one day a
week, every n weeks, where n > 1, are possible on the pilot but
not in plan. Signal them as unsyncable, rather than converting
them to once-per-week repeats (Thomas DeWeese). Show progress bar
while reading Pilot records. Re-fix bug about plan alarms getting
turned off that was supposed to be fixed in 1.108 but really
wasn't. Fix some bugs related to time zone conversion: end date
of repeating appointments would move back a day when synced from
pilot to plan in time zones east of GMT, and appointment times
shown in the log window would be in GMT rather than local time.
* SendMail conduit: fix bug that comes up when the database
doesn't exist on the pilot.
* Remove contrib/dinesh-dutt, which was an old version of software
that was later distributed on its own (the syncbbdb project on
sourceforge, not to be confused with syncbbdb2, which is an
unrelated project and is the one I recommend for bbdb syncing).
Changes from v1.107 to v1.108
* Add error checking throughought PilotManager and several
conduits to fix a bug that caused data loss when the link to the
pilot was lost during a sync.
* Only load active conduits, rather than all conduits, at
startup. This means that you no longer need to rename or delete
unused conduits that have missing dependencies. As a side
effect, the "Load New Conduits..." menu item is gone, replaced
by a "Rescan" button on the "Properties" dialog.
* Changes for compatibility with pilot-link 0.12.0. Backwards
compatibility with earlier pilot-link versions is matained.
* Changes for compatibility with Tk 804. fixes bug causing some
color preferences to be ignored when using Tk 804, and fixes
buggy behavior of the Up and Down buttons in the Preferences
dialog.
* Fix pcid corruption in preferences file that could cause every sync
to be a full sync.
* Fix hang when trying to sync to a USB device that wasn't connected.
* Applied patch to fix problems with PalmOS 3.5 and above.
* Fix purely cosmetic y2k display bug.
* Use Digest::MD5 instead of the deprecated MD5.
* Patch from NWalsh to lib/perl5/PilotSync.pm, fixes unreliability
problems, esp. with newer versions of Perl.
* Change the dates in the log messages to be ISO compliant instead
of US-centric mm/dd/yyyy (Mark Staveley).
* Replaced Setup script with Setup.pl. The script is no longer
invoked automatically the first time PilotManager is run; rather,
it must be run by hand (perl Setup.pl) to create the executable
PilotManager.
* If Setup.pl is given a -conduitdir argument, then PilotManager
will look in that directory for loadable conduit modules (in
addition to the directories it already looked in).
* Updated developer contact information
* Backup conduit: update to version 1.008, which had been released
separately as 1.008ea.
- Better, more consistent filename handling throughout.
* Installer conduit: update to version 1.009, which had been released
separately as 1.009ea2.
- Recognizes .pqa files as well as .pdb/.prc.
- Only use included "MultiFileSelect.pm" with Tk 4.0,
otherwise, use Tk::Fileselect module.
- Print message after each file is installed.
* SendMail conduit: new version 0.900
- only perform wordwrap on body of mail message, not
headers. (Chris Waters)
- Check for I/O errors (see comment at top of ChangeLog)
* SyncAB conduit: no changes, version number stays at 0.96 BETAp1.
* SyncCM conduit: new version 1.103
- Check for I/O errors (see comment at top of ChangeLog)
* SyncFood conduit: no changes, version number stays at 0.96 BETA.
* SyncMemo conduit: new version 1.9 integrates changes from
version 1.8-ea2, which had been released separately, plus
additional changes.
- from 1.8ea2: Use internal checksum function instead of
Shell::sum.
- from 1.8ea2: Use internal isPilotText function instead of
Shell::file
- from 1.8ea2: Use opendir/readdir/closedir for directory access
rather than relying on globbing. Fixes breakage when category
names have whitespace.
- Eliminate discrepancy between behavior of full sync and fast
sync. In earlier versions, a memo deleted from the desktop would
be deleted from the pilot during a fast sync, but recopied from
the pilot to the desktop on a full sync. A preferences option
allows you to keep the old behavior if you wish.
- Process all file deletions before any file creations, to avoid
unnecessary file name collisions.
- Use gtkdiff or tkdiff if filemerge not available (Mark
Staveley). Better would be to allow merge program to be chosen
via the configuration gui--patches welcome.
- Remove special characters from filenames (idea from Mark
Staveley)
- Increase maximum file name length (Mark Staveley)
- Check for I/O errors (see comment at top of ChangeLog)
* SyncPlan conduit: new version 0.97 integrates changes from
version 0.96BETA, which had been released separately, plus
additional changes.
- from 0.96BETA: Support for weekly appts from pilot with
frequency > 1 (patch by Alan Harder based on changes in
sync-plan)
- from 0.96BETA: Fix repeat end date for daily repeating plan
records (patch by Alan Harder based on research by Aaron
Kaplan)
- from 0.96BETA: Patch to support plan records with two alarms
(just use earlier one for pilot) by Kevin Fink
- from 0.96BETA: Configurable level of verbose output and
configurable netplan port, patch by Andreas S. Oesterhelt
(oes@paradis.rhein.de)
- Fix a bug that caused deleted records to reappear when
syncing one pilot with more than one desktop machine.
- Fix a bug that would cause an alarm to be disabled in plan if
the appointment was modified on the pilot. As a side-effect,
any appointment created on the pilot will now have an alarm
set in plan.
- Check for I/O errors (see comment at top of ChangeLog)
* Updated version of contrib/alan-harder/UpdateMemos.pl
* Added SyncAB_plusBBDB to contrib/dinesh-dutt. This had never
been released as part of a PilotManager package, but was available
separately on moshpit.org. Since I'm already supporting
SyncBBDB, I don't intend to support SyncAB_plusBBDB.
* SourceForge CVS repository set up (Chris Waters)
* Development now coordinated by Aaron Kaplan
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.
foo-* to foo-[0-9]*. This is to cause the dependencies to match only the
packages whose base package name is "foo", and not those named "foo-bar".
A concrete example is p5-Net-* matching p5-Net-DNS as well as p5-Net. Also
change dependency examples in Packages.txt to reflect this.
