http://prdownload.berlios.de/kmobiletools/kmobiletools-0.5.0-beta3.tar.bz2 Changelog: 2007-06-05 KMobileTools 0.5.0_beta3 * Including 19200 baudrate. * Fix that allows to try fetching SMS even from phones that don't have SMS slots. * Adding support for the incoming kdebluetooth-1.0-beta3. * Fixing user interface issues for SMS CVS exporting. * Fixing SMS exporting to maildir (thanks to cerebro84 at gmail dot com). * Some autotools fixes. * Adding a working gammu engine, thanks to Matthias Lechner. * Adding KNotify support, and making it configurable in the user interface. Built/installed using the beta2 ebuild. Reproducible: Always
While renaming ebuild is sufficient to build and run kmobiletools, please consider adding experimenal support for building with gammu backend. (perhaps introducing new gammu useflag). Upstream says one needs gammu-0.10.6, which is currently skipped in portage (as it is a development version), but I'll test how it does with gammu-0.11.0 which is currently in portage and should be definitaly same as 0.10.6 with couple of bugfixes.
Created attachment 122067 [details, diff] kmobiletools-0.5.0_beta3-no-automagic-deps.patch This patch fixes 3 automagic dependencies in kmobiletools-0.5.0-beta3 (by adding --enable-obexftp, --enable-p2kmoto, --enable-kdebluetooth configure switches) and also fixes build of gammu engine (one line change). The automagic deps patch is already merged upstream (see http://websvn.kde.org/?view=rev&revision=675599 ) and the gammu build fix is from svn. (thanks Marco Gulino, kmobiletools dev) We can safely make more dependencies conditional with this patch. (my resource: http://www.gentoo.org/proj/en/qa/automagic.xml ) My ebuild for beta3 will follow.
Created attachment 122069 [details] kmobiletools-0.5.0_beta3.ebuild Differences between beta2 and beta3 include: * inheriting eutils because we use (should we inherit it when it is already inherited in kde.eclass?) * adding bluetooth, gammu, obex to IUSE. gammu is not used anywhere and should be commited to use.local.desc. I haven't found existing appropriate useflag. obex is already local useflag for syncml ebuilds * changes to DEPEND now we depend conditionally on kdebluetooth, thanks to above patch. /me tested it with and without bluetooth flag, both work okay. new conditional dependency on obexftp, to enable obex2 kioslave. I choose 0.21 version because it has same stable state as 0.19 but works even with -Wl,--as-needed. (you can now access mobile filesystem as mobile:/ ) new conditional depencendy on gammu. Although webpage says one must build against 1.10.6, building against 1.11.0 works well and behaves the same way * self-descriptive changes to src_unpack * changes in myconf: fixing (use_enable kde kontact-plugin): ./configure --help of kmobiletools-0.5.0-beta2 was not true. (see patch above) adding bunch of other configure switches (mostly avoiding automagic dependencies and introducing new options) * self-descriptive changes in pkg_postinst Testing and feedback welcome. Matej Laitl
you should move the DBUS checking _BEFORE_ checking for kdebluetooth, otherwise kdebluetooth beta3 will never be detected (the dbus stuff is meant to set also the correct CXXFLAGS for kdebluetooth).
Created attachment 122243 [details] kmobiletools-0.5.0_beta3.ebuild Please address the issue described in comment #4 and base any further work on this ebuild.
Created attachment 122250 [details, diff] kmobiletools-0.5.0_beta3-no-automagic-deps.patch Thanks for pointing this out, Marco. Fixed checking order (partially reverting to old code). Here you can check it: checking kdebluetooth/rfcommsocketdevice.h usability... yes checking kdebluetooth/rfcommsocketdevice.h presence... yes checking for kdebluetooth/rfcommsocketdevice.h... yes checking for "dbus-1"... yes checking DBUS_CFLAGS... -I/usr/include/dbus-1.0 -I/usr/lib/dbus-1.0/include checking DBUS_LIBS... -ldbus-1 checking libkbluetooth/adapter.h usability... no checking libkbluetooth/adapter.h presence... no checking for libkbluetooth/adapter.h... no Tkanks for tuning my ebuild, Wulf, now everything should be ready.
Thank *you*, Matěj, for this ebuild. I'm going to wait for any other comments for about 24 hours and will check it in afterwards if nothing has turned up by then.
24 hours sometimes feel much longer than they should be, don't they? ;-) I've just checked this in to CVS.
Thanks :)
