summaryrefslogtreecommitdiff
path: root/packaging
diff options
context:
space:
mode:
authorEric S. Raymond <esr@thyrsus.com>2013-11-13 01:31:16 -0500
committerEric S. Raymond <esr@thyrsus.com>2013-11-13 01:31:16 -0500
commitb360367d400735a46c98f0fc0a604b479c19a1b2 (patch)
treefb299687d98405fd1902fecf4b9a30404894ef23 /packaging
parent58f23c6e2b2f3778fcf86cc5783c0977e45fa87f (diff)
downloadgpsd-b360367d400735a46c98f0fc0a604b479c19a1b2.tar.gz
More hints for packagers.
Diffstat (limited to 'packaging')
-rw-r--r--packaging/readme.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/packaging/readme.txt b/packaging/readme.txt
index d6651774..1fa13e2f 100644
--- a/packaging/readme.txt
+++ b/packaging/readme.txt
@@ -6,8 +6,8 @@ in desktop packaging.
Usable deb and RPM specifications have their own subdirectories here.
Our package files want to set up a hotplug script to notify gpsd
when a potential GPS device goes active and should be polled. The
-goal is zero configuration; users should never have to tell gpsd how
-to configure itself.
+goal is zero configuration; users should *never* have to tell gpsd how
+to set itself up.
Bluetooth has a requirement to be able to write to the gpsd control
socket from a userland device manager. Accordingly, you probably
@@ -27,7 +27,8 @@ figures out which group it should move to by looking at the ownership
of a prototypical tty (look in gpsd.c for this code) but the owning
user and group can be compiled in with build-system options.
-Make sure whatever group gpsd lands in has dialout access - otherwise
-your users will see myerious failures.
+Make *sure* whatever group gpsd lands in after privilege-dropping has
+dialout access - otherwise your users will see mysterious failures
+which they will wrongly attribute to GPSD itself.
// end