© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
> The items I thought about addressing first are (because they are easy
> and all about packaging):
> What do you (two) think ?
First of all, I would like to see the package in revu:
https:/
https:/
So that we can use it to coordinate our efforts. The only thing I would like
to ask you is to keep to a minimum the number of upload so that we can track
all the changes in an easy and coordinated way.
> - Create init.d script (will help with the path issue below)
Concerning the daemon initialisation, you should refer to the debian policy:
http://
http://
The scripts in /etc/init.d should be good examples of how to write the init
script.
The dmraid package should give you an idea how to install and start it
(basically, its just a question of installing the script in /etc/init.d and
registering it with update-rc.d during postinst, which is done calling the
dh_installinit debhelper)
> - Move murmur.ini to /etc/murmur (nb: I didn't manage to locate it
> after running the server)
> - Move murmur.sqlite to /var/lib/murmur (currently it shows up in /usr/bin)
> - Move murmur.log to /var/log/ (currently it shows up in the current
> directory) - Move murmur.pid to /var/run/ (currently it shows up in the
> current directory) - Move the .pl in /usr/lib/cgi-bin (there is also some
> perl dependency missing)
Concerning the locations, again the policy is the best available source:
http://
http://
As you already correctly said:
configuration files go to /etc/mumble
log files in /var/log/mumble (there should be a configure option)
pid files in /var/run/mumble (there should be a configure option)
pl files in /usr/lib/
I don't think /var/lib is a good place for murmur.sqlite, shouldn't be
in /etc/ too?