Re: Trouble compiling from CVS

["Jorge Enrique Gomez G." <jorgee somnoliento com>]

Thanks for your answers. 

I finally got something working. Here's what I did, following David's
suggestions: 
* I removed every RPM related to gnome-pilot and pilot-link (to the
point that 'rpm -qa | grep pilot' returns nothing) 
* Instead of compiling pilot-link from CVS, I used the developer release
(0.10.99), got it to compile and installed it.
* I patched the gnome-pilot files with the usb code, compiled and
installed it.

The palm (m125 usb) is now recognized not only by the pilot-link
utilities (like pilot-xfer) but also by the gnome apps like
gpilotd-control-applet (although the icons to setup the palm and its
conduits are gone from the control center, I don't know why).

I added the PilotSync Applet to the toolbar, and it responds when I
press the HotSync button on the palm's cradle. For now I'm just using a
generic "backup" conduit, and that seems to be working fine.

How do I get the "real" conduits back? (either for gnome-pim or ideally
for evolution) are they independent from the implementation of
gnome-pilot? that is, shouldn't they run ok, isolated from the details
of how the daemon communicates with the palm?

Thanks,

--
Jorge