Attached patch contains a small modification of the kpilot ebuild. The patch {en/dis}ables the mal conduit. Also I strongly suggest to stabilize kpilot-3.5.7 as soon as possible because it contains some fixes for serious bugs. I've seen that pilot-link-0.12.2 is in portage now. I use that version for about half a year now and it works perfect here. Reproducible: Always
Created attachment 130485 [details] Patch to enable/disable mal
Created attachment 130487 [details] Patch to enable/disable mal. The previous patch was in the wrong direction =:)
And what should that use flag do? It doesn't do anything with your patch, except for making a library dependency optional without affecting configure/compile in any way - that's not a valid usage of USE flags.
No additional actions are needed. The kpilot configure script will disable the mal-conduit if it doesn't find mal. So this flag enables you to install kpilot without the mal-conduit and therefore without the libmal dependence. The mal conduit is for syncing avantgo which is not supported by every pda, or at least not used by every user. (At least not by me ;)
(In reply to comment #4) > No additional actions are needed. The kpilot configure script will disable the > mal-conduit if it doesn't find mal. Which is completely broken behaviour, please see http://www.gentoo.org/proj/en/qa/automagic.xml
Gah, i see =:(. Ok sorry for bothering then... I don't think so it's very usefull to invest more time in this because we're focussing on getting KPilot trunk stable. I'll make sure we can get a bit more advanced ebuild, which makes it possible to {en/dis}able conduits for that one. (In reply to comment #5) > (In reply to comment #4) > > No additional actions are needed. The kpilot configure script will disable the > > mal-conduit if it doesn't find mal. > > Which is completely broken behaviour, please see > http://www.gentoo.org/proj/en/qa/automagic.xml >
Err, just found out that mal can be disabled by passing --disable-mal to the configure script. I don't know how to add that in the ebuild. If you could give me a hint on that i'll adjust the patch and test it.
Created attachment 130512 [details] Made mal conduit optional Did some research myself. Added --disable-mal to $myconf when the useflag is not set.
$(use_enable mal) is better, but anyway please reopen this bug.
