Re: SNAFU: Incomplete installs, no conduits available, precompiled packages not working

["David A. Desrosiers" <hacker gnu-designs com>]

> But how could I then start gpilotd manually, if it's not in the path?

	You only need to start it manually for testing/debugging purposes.
Once you start it, and exit GNOME, it will continue to be started
automatically. It will also be started (and stay resident) if you launch the
gnome-pilot configuration applet and modify any settings.

> bash won't let me execute a binary it can't locate for me ;-) And by the
> way, after installing Jamie's packages, gpilotd lives in /usr/bin again
> and /usr/libexec is empty.

	Well, I hope he fixes that to remain current with the upstream
method, which definately does not put it in /usr/bin. How old are these
packages?

> Maybe, if I get very bored the next days, I'll set up woody on my big PC
> and try it again there, on a fresh install.

	If you have any comments or things you noticed that are missing in
the HOWTO, let me know, and I'll be sure to update it to reflect those
changes.


d.