> You received this message because you are subscribed to the Google Groups "kippo users" group.
> To post to this group, send email to kippo...@googlegroups.com.
> To unsubscribe from this group, send email to kippousers+...@googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/kippousers?hl=en.
I made a debian package of kippo at some point (and got frustrated by various
things and forgot about it), so I have a special interest in how it's built.
I installed it and took a quick look at what's installed and where. Some
It creates a /.pc/ directory and /.pc/debian-changes-0.5+svn20110716-1 on my
server. Never seen this before by other packages.
The init.d script looks short and sweet, but could maybe use the pidfile to
kill the process?
About kippo.cfg - the debian way would probably be to install kippo.cfg
instead of kippo.cfg.dist. If needed, the service could be disabled by default
by a config setting or an environment variable stored in /etc/default/kippo.
Maybe the binaries like playlog.py should be in some PATH directory. Since
their names are kinda generic, maybe the package could rename them to
something like kippo-playlog, kippo-createfs, ...
The file paths are looking good to me - packaging like this is exactly why
every path is configurable in kippo.cfg :)
There's i386 and amd64 versions of the package, while kippo is actually
arch-independent (being all python). I've forgotten now how this stuff is
handled in debian packaging, but my package ended up as *_all.deb. I can
investigate this more later.
Thanks for working on this!