PICCORO McKAY Lenz writes:
In your packages, your configuration separates too many packages into various configurations without taking into account if there are changes, for example courier-webadmin-apache2 but I don't see for lighttpd or nginx
That's because I don't use them and don't have this domain knowledge. If someone needs this, they're welcome to contribute patches but I cannot do everything myself.
The subpackage-based approach makes this seamless. Installing Courier should then automatically install the appropriate subpackage with the configuration files for whatever web server is installed. And it won't install configuration files for the web server that's not installed.
Debian's packages either do not install any apache configuration files; or they always install them, even if apache is not installed; or the installation script manually installs them after checking if apache is installed. Those are the only possibilities.
And neither approach is superior to the much simpler packaging-based approach. Why install configuration files when they not are needed? And why go through the complexity of writing a tailored script, that can potentially break or do something wrong? Why is this complexity even needed? This is what package managers are for. This is the package manager's job. This is exactly what Recommends: is for, and the right thing happens automatically, without a single extra line of scripting. I see no need to reinvent the wheel, just let the package manager figure out what web server is installed, and install the appropriate set of config files for it instead of having to write your own script for it.
that they are much more efficient than the fat apache2, and even so the package just places the configurations but does not take into account if it was altered in updates or upgrades ..
There's not a lot to alter. And even if someone needs to change something: there's nothing to prevent anyone from not enabling the default config, but installing their own tailored, that upgrades won't touch.
Sam, debian packages follow standards to integrate into the system, taking into accoutn the mayor and minor upgrades.. very valuable for production sites..
I don't need a tutorial about Debian standards. I don't need to be scolded by these "Debian standards" that I have an executable-is-not-world-readable or a non-standard-setuid-executable-perm. Debian seems to know better how individual software packages should be considered, then the packages themselves.
I'm just curious about the average number of lintian-overrides per package, in Debian. I found Debian's standards to be such a distraction that I had to write my own script that runs lintian and automatically converts its noise into overrides. I would not be surprised to learn that many others do the same.
In conclusion your packages are more "easy to produce" rather than "easy to manage in upgrades", especially major upgrades when the whole system changes.. I hope you understand.
I think I'll wait and let time decide which version is easier to work with.
NOTE ABOUT MAILDROP AND WEBADMIN: those are provided, maildrop just packages separatelly, and webadmin in build in.
No.maildrop and courier-maildrop are configured differently. Debian either packages the standalone maildrop package only, or packages Courier's maildrop as a standalone package.
Either way the end result is subtly incorrect and resulted in issues for people, over the years. This is plain wrong.
Ditto for sqwebmail.
pgpZNaTucHHZG.pgp
Description: PGP signature
_______________________________________________ Courier-imap mailing list [email protected] Unsubscribe: https://lists.sourceforge.net/lists/listinfo/courier-imap
