Re: gpsd re-write

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24-01-10 14:22, Michael Lippautz wrote:
> Hej,
> 
> As I am re-writing the gpsd package, a few questions did come up.
> 
> 1) gpsd can deal with multiple different gps devices (being served as
> different nodes). Is it sufficient to start gpsd with a control socket
> and add recipe for gps devices that just add init script that are
> executed after gpsd startup. These init scripts could add the device
> over the control socket. I.e. a recipe gpsd-device-... could add the
> /dev/ttyACM0 node, using the control socket.
> 
> 2) Since gps devices can also be integrated into platforms (machines)
> a second approach using RDEPENDS_${PN}_machine can be used to build a
> machine specific package. This machine specific package could init the
> device and also attach it using the socket.
> 
> Is it "ok" to create such machine specific packages, i.e.
> gpsd-hardware-om-gta01 ? How about "device" specific recipes (should
> they be done in an other way)?
> 
> Additionally I can also add an /etc/default/gps-hardware file that
> uses update-alternative to add the device at program startup.
> 
> Are these approaches correct? Don't want to sit and write these if
> they are rejected anyways ;)

Your approaches are a lot better than the current 'gpsd only starts if
it was built for your machine *AND* OE has a config for it'

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLXGK4MkyGM64RGpERAk7CAJ4kbdekGFkioFbpHZ/28fsmqcOqtACfQgx3
i5aHG9ULaUksACfO759u7sc=
=VAwM
-----END PGP SIGNATURE-----