[pkg-fso-maint] abyss again [sponsor needed :-) ]

[Nikita V. Youshchenko]

> from what I have seen in my /usr/share/dbus-1/system-services-directory
> most services are in /usr/lib/pkgname/prog or /usr/sbin/prog.

That looks consistent.

If a service daemon is intended to be started by dbus daemon only, it has 
nothing to do in $PATH, thus FHS-compliant location is under 
/usr/lib/pkgname/

If a service daemon could be started manually sometimes, then /usr/sbin

Anyway not /usr/bin because daemons are not started by "normal user".

In our case, /usr/sbin looks to be the best location, because starting from 
dbus leads to timeouts. So manual start cound be better - perhaps 
from /etc/init.d/frameworkd? or from an individual init.d script? maybe 
controlled by a flag under /etc/defauts/?

> But as I don't know if anything will break between the new libs and
> fsousaged (for me it worked at last) would it be possible to upload
> fso-usaged as it is for now?

Already uploaded :)

> I will need to touch fso-usaged and libfso-glib again, to resolve
> #547204 but am still in communication with upstream about solutions. So
> the move to /usr/sbin could also happen then.

Ok

Nikita
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-fso-maint/attachments/20090927/c8822606/attachment.pgp>