big changelog is there : http://multisync.sourceforge.net/releases/release_notes_081.shtml as every gtk1 => gtk2 move, large parts of the ebuild could change should close those 2 at the same time : http://bugs.gentoo.org/show_bug.cgi?id=29365 http://bugs.gentoo.org/show_bug.cgi?id=33608 Reproducible: Always Steps to Reproduce: 1. 2. 3.
i put tad@gentoo.org in CC as he was assigned the 2 previous bugs about multisync
i think tad is in the pda herd/list already ..
Created attachment 22378 [details] ebuild for Multisync 0.81 I've created an ebuild for Multisync 0.81 based on the 0.80 ebuild. I only had to change a few lines and I haven't incorporated any of the changes needed for libwxml support for Nokia phones. I haven't tested palm sync settings since I don't have a palm or the needed libraries and the csa_plugin requires libraries that no ebuild exists for so I left that out. My library requirements should be checked as well since I'm running the latest of everything and may not have bumped up the requirements accordingly.
I've installed Multisync 0.81 based on a hacked ebuild I made myself. It works fine, but I've a comment on the suggested ebuild. Perhaps irmc stuff should probably be divided up into irmc-ir and irmc-bt. If you're using Bluetooth, you don't need irda-utils, and if you're using IR you don't need bluez-utils. This should go into portage ASAP, IMO - the dependencies on the current ebuild are a mess - they try to install an old version of Evolution with dependencies on Mozilla, etc. Alex
The deps should only be trying to install an older version of Evolution if you have USE="-gtk2 evo", in which case it will pull in evolution-1.2* which is gtk1 based. multisync-0.81 has been committed to CVS, closing.
This is marked as a mandatory dep : >=gnome-base/ORBit-0.5.17 but it is gnome1 only it is named ORBit2-x.y.z in gnome2
Created attachment 23609 [details] multisync-0.81 including palm_sync Hello, When I tried to emerge multisync-0.81 and found out the palm_sync plugin wasn't built, I tried to edit the ebuild to include it. Building the plugin dies in: checking for pi_socket in -lpisock... yes checking pi-socket.h usability... no checking pi-socket.h presence... no checking for pi-socket.h... no configure: error: You must have the libpisock-dev package installed. ...during configure. Building the palm_sync plugin and/or multisync from the source at their website does the same. However, the missing file is available on my system at /usr/include/libpisock/pi-socket.h, as part of the app-pda/pilot-link package. Compiling pilot-link from original source seems to give the exact same file. The only problem the ebuild seems to have, is not finding the pi-socket.h file. I can code a little although I have no experience with C, so I'm don't know how to solve the problem (although it seems to me this could be as easy as adjusting a path somewhere). For now, I'm willing to test any adjustments and offer any other help on this ebuild :) To reproduce: USE="+pda" emerge multisync (using attached ebuild)
Stephane, The ORBit/ORBit2 error was mine I was not aware of the differences (I'm predominantly a KDE user). DEPEND has been fixed and now includes ORBit2. Should the versions of ORBit/libbonobo/libgnome as well as Evolution be determined by the gtk/gtk2 USE flags?
well, from what i know, support for gtk1 was totally removed (might be wrong) so, there should not be anything about evo 1.2 or gtk1 with a multisync 0.81 ebuild. gtk1 only users (hum, who uses that ????) would have to stick to 0.80 or older
Checked the multisync changelog for 0.81, GTK+-1 support has been deprecated. DEPENDS fixed to reflect this, evo USE flage now only depends on evolution-1.4*. Finaly closing this bug. Stephan, thanks for the help and your patience.
