[pkg-lighttpd] Bug#642604: Bug#642604: lighttpd always binds to IPv6 on TCP port 80

[Arno Töll]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hello Adam,

On 29.09.2011 07:25, Adam Nielsen wrote:
> That's a fair point, and to explain my reasoning in a bit more detail,
> my problem is that I want to leave the Debian-specific parts of the
> configuration alone.  At the moment there is one config file that sets
> everything, from Debian-specific options like log and pidfile paths to
> generic options like index-file names, as well as user-configurable
> options like listening port numbers.

I get your point, but I consider every setting in /etc specific to
Debian, but yet allowed and suggested to be changed by the user.

Note, we don't distinguish between settings supposed to be changed by
users and those considered a distribution specific detail. Of course it
does not make too much sense to change things like the pidfile setup,
but on the other hand, that's totally left to the user and we should
support that.

Also I am pretty sure, whatever we choose, some other users will
disagree and fine some other partitioning more useful.

> My personal opinion is that it would work best splitting lighttpd.conf
> into a couple of files, outside the conf-available directory.
> 
> One of these could be named debian.conf (or platform.conf) and contains
> all the log/pidfile paths and other options that should not normally
> change if you're doing things the Debian way, and it would be maintained
> by the package manager so it could potentially be updated if something
> specific to Debian changes.

Well, you realize you still have to have something like "include
debian.conf" in the main lighttpd.conf which would hardly be the same on
all Linux distributions?

Note, we do upgrade configuration files anyway. Whenever you update
Lighttpd to a new version, your configuration file will be replaced by
our new configuration (presuming you didn't change it). If you changed
it, you are being prompted what dpkg shall do and differences are shown
to you. See [1] for details on how conffiles (lighttpd.conf is such an
example) are handled in Debian.

> At any rate, lighttpd.conf would then include these files and the
> conf-enabled ones so that people such as myself could simply replace the
> default.conf as needed, and not have to worry about keeping any of the
> platform-specific options up to date.

So, to summarize: you want:

/etc/ligttpd/lighttpd.conf:
  + include debian.conf
  + include default.conf
  + include_the_conf_enabled_stuff

debian.conf: distribution specific settings (pidfile, user name?)
default.conf: everything else


[1] http://www.debian.org/doc/debian-policy/ap-pkg-conffiles.html

- -- 
with kind regards,
Arno Töll
IRC: daemonkeeper on Freenode/OFTC
GnuPG Key-ID: 0x9D80F36D
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJOhQJhAAoJEMcrUe6dgPNt9tMP+QEBNpmeTYnKLRkGolx+Au/X
sNopq1zh3HtJntArtDz4HsFnAIbal6KD+2oTYPXUJ+N8gnxo9dHA7e1tFST7bJ2p
umRPwmiNfCLyF8QG5JjcNqrQY/sKXfZlCrTDlSD1zZP72vUo+5HbyW+zOJ0VlsX8
RLkLLcSuFzf4Tf2NHNzpb6XUgyhCOZPj3ChKdsd/H8XTzmldMV5DKHJy6xtzM/ma
XZE/a/QakPVz4EoYHXuwwxVUUwFA0J9a1TPy6SoblU6hSL1jqAqBvzODVswU0XBo
NtdU0WZ6weGFO5WHERRaTjkiMm7QpWY9aujmT7ZlJ9fkYQqQtZxDb8pDqhhjj2x8
TFAz+2PQI7dLUKQRUZOj1np6CKNLxFkavv2jc+FRr6wayMw9n0klTk3pCT17n9Ky
9x1C3UQK3Exhn6pSe7Q11iK+y1ALBX/xBk51KLOkiTHOcYa3illaWHWXwa7wL7Zf
aj35OSLlWv45ZTxOWZa62Wu/J+Nx3NMiIp1LIhOh+n8gExFeixjUkmB521f/NDnE
ZwNYN4vkwmXXI9BiQdsZLuZozddFnwrfs+Gl7tBsIObbEuTyEcyHZKppgcq8aADw
xN/Ct+CdjJ9A4A0cXPqtYwpzf3r6USFUNg80QDAQsG9En827f3QHePZ/yxcyTLSb
JUtck1IqIG37v5l9Qmyt
=ViA9
-----END PGP SIGNATURE-----