gypsy

svn path=/ebuilds/; revision=111

1 files changed, 22 insertions, 0 deletions

diff --git a/sci-geosciences/gypsy/metadata.xml b/sci-geosciences/gypsy/metadata.xml
new file mode 100644
index 0000000..eb84513
--- /dev/null
+++ b/sci-geosciences/gypsy/metadata.xml
@@ -0,0 +1,22 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE pkgmetadata SYSTEM "http://www.gentoo.org/dtd/metadata.dtd">
+<pkgmetadata>
+<herd>no-herd</herd>
+<maintainer>
+	<email>bangert@gentoo.org</email>
+</maintainer>
+<longdescription lang="en">
+Without some sort of multiplexing system, a GPS device can only safely be accessed by one client. In a server situation this may not cause any problems, but on modern desktop which could potentially have multiple location aware devices, this could be an issue.
+
+Gypsy hides the tricky details of parsing NMEA from the client applications, passing the data as simple values for the clients to use.
+
+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.
+
+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)
+</longdescription>
+</pkgmetadata>
+