The abook maintainers have provided a new release tarball. Due to
some issues at the maintainers end, the release is located here:
http://abook.sourceforge.net/devel/abook-0.6.1.tar.gz
This release includes debian bug fixes, vCard support and the ability to
customize data views. I was able to build using autoconf 2.69/automake
1.14 environment variables, aclocal and automake --add-missing.
Oddly, when I pulled the latest source from the Debian repositories,
automake/autoconf were not needed.
I think I can update the port (porting newbie) but have several
questions.
The main reason, IMHO, to update is to allow import/export of the
contacts to other popular email addressbooks. I have tested abook
generated ldif files into Sylpeed/Claws-Mail but have not tested
import/export abook data <--> Evolution, Thunderbird, Outlook, MS
webmail, Alpine, Mutt aliasis or any ldap servers.
The second reason to update would be for the OpenBSD port to be current
with Debian+derivatives. If this is the case, would it make sense going
forward to pull patched Debian source? There does not seem to be a
Debian MASTER_SITE but I have seen ports where this has been done.
Presently mutt installs as a default email client in their Xfce4
and LXDE installs so I think the Debian group has a significant
incentive to provide a functional addressbook.
With that background, the questions:
1) Pull source from SourceForge /devel or Debian?
2) Interest in testing import/export or provide the update and let
upstream deal with import/export problems?
3) Would a post-extract/post-patch
post-patch:
@cd ${WRKSRC} && env AUTOCONF_VERSION=${AUTOCONF_VERSION} \
AUTOMAKE_VERSION=${AUTOMAKE_VERSION} PATH=${PORTPATH} \
sh bootstrap
be a more elegant way to generate aclocal.m4 and automake --add-missing?
--
J. Scott Heppler
