[Pkg-glusterfs-devel] Comments on Debian packaging

[Jeremy Lainé]

Some more comments:

- glusterfs-server.postinst file was incorrect (fixed):
* communicating with the user via maintainer scripts is discouraged, a
README.Debian file is more appropriate
* as glusterfs-server.postinst had no #DEBHELPER# tag, the
automatically-generated part of the postinst script (registering
/etc/init.d/glusterfs-server) was not included
=> I have added a README.Debian and removed the postinst script

- debian/control (fixed):
* Standards-Version should be 3.7.3
* libfuse0 should be in Section libs
* libfuse-dev should be in Section libdevel
* no need to repeat Section / Priority for binary packages when it's the
same as for the source package

- mount.glusterfs needs a manpage (at least a minimal one)

- glusterfs-server / glusterfs-client / glusterfs-examples : do we
really need separate packages for all these, or would "glusterfs" be OK?
I am not sure what to do here yet.

- /etc/init.d/glusterfs-server : would need to be rewritten to be based
on /etc/init.d/skeleton with as few changes as possible. The biggest
problems here are:
* the return codes do not follow the Linux Standard Base standards
* force-reload (alias for restart) is not implemented
* why the hand-written code that handles the PID file? doesn't
start-stop-daemon work correctly?

- /etc/glusterfs/*.sample : I think these files should really be in
/usr/share/doc/glusterfs/examples/. The problem here is that anything in
/etc is considered as a CONFFILE, meaning local changes are preserved on
upgrade, and this does not make sense for example files. Will think
about this some more.

Jeremy