On Mon, Feb 28, 2005 at 08:50:07PM +0100, Daniel Baumann wrote: > Sure, patches are always welcome. The reason why non initd-configuration > was done until now is, that it the configuration should not depend on > one certain initd, but do some autodetection or whatever to work with > all of the several initd packages.
Ok. No patch yet, but a few questions or thoughts that might lead to one. Obviously there is a update-inetd script in the netbase package. From what I can read out of it's documentation and by reading the actual script it does only care about the standard /etc/inetd.conf file. Implementaions using other files are ignored. Since debian provides the mechanism for updating inetd records in a package from the Important section and other packaged software uses it, micro-httpd probably should too. Dealing with the several inetd:s available is update-inetd's job and the fact that it doesn't handle at least xinetd is a bug that should be reported against netbase if it isn't already there. (I do not have net access to be able to check now) One might wonder what group in the file a web server should be placed under. My guess is that INFO would be the most appropriate? Following how debian treats other webservers I guess www-data should be the user and /var/www the path for web pages resulting in the magic line: update-inetd --group INFO --add "www stream tcp nowait www-data /usr/sbin/micro_httpd micro_httpd /var/www" Other packages seem to have a few lines to test for existance of the script in their postinst and of course some lines to remove the configuration in their prerm. Of the packages I have installed on my system tftpd-hpa is the one with the best examples of these scripts. Since that package even uses the same licensing as micro-httpd, except for the advertising clause that don't apply to debian scripts anyway, it would be pretty straigt forward to reuse those files. Should I make that patch coming or do you think you can handle copying and modifying two scripts from another package well enough on your own? -- /Martin
signature.asc
Description: Digital signature
