* Ian Darwin wrote: > Gypsy is a gpsd replacement, used by OpenMoko "FSO" distribution. > > Compiles and runs; not yet tested with an actual GPS connected (left my > puck GPS at home this week). > > $ more pkg/DESCR > Gypsy is a GPS multiplexing daemon which allows multiple clients > to access GPS data from multiple GPS sources concurrently. > > Gypsy uses D-Bus to notify clients about location changes, sitting > on the system bus, issuing signals as the GPS data changes. This > design allows clients to only be notified about the changes they > care about and ignore the rest. Gypsy has fine grained signals, so > a client only interested in position changes will not be woken up > for any other changes like, for example, satellite detail changes. > > Gypsy is designed to be usable on all manner of systems, from low > powered devices (such as Nokia N810 and Openmoko Neo) to regular > high powered desktop systems. As the signals it emits are fine > grained applications are woken up only when they absolutely need > to be, keeping power requirements to a minimum. > > Gypsy was designed to fix "the numerous design flaws found in GPSD". > These are compiled at http://gypsy.freedesktop.org/why-not-gpsd.html.
So how does this compare to gpsd for real applications? I am asking since the main gpsd developer is also an OpenBSD developer, and maybe there are ways to fix the problems in gpsd? Oh, and I find this rude. > > Included with Gypsy is libgypsy which is a GObject based C wrapper > for the D-Bus API making writing clients very simple, although any > language with D-Bus bindings can be used to write a Gypsy client > (See simple-gps-python.py in the Gypsy sources for an example written > in Python). > -------------------------- > Port is at http://www.darwinsys.com/openbsd/myports/gypsy.tar.gz > -- Marc Balmer, Micro Systems, Wiesendamm 2a, Postfach, CH-4019 Basel, Switzerland http://www.msys.ch/ http://www.vnode.ch/ "In God we trust, in C we code."
