Hello all, Are there any packaging guidelines for building RPM packages? Not how to build the rpm, but how to make a freshly installed package "behave".
The reason that I ask is that I've been looking at the OpenPKG Postfix RPM and notice that, as installed, it will NEVER work correctly, something contrary to how the author expects his software to be installed[1]. Specifically: - the provided main.cf configuration file only allows connections from and to address 127.0.0.1 effectively disabling all non-local network activity.[2] - the provided main.cf configuration file specifically sets various dummy configuration values which are WRONG (in the sense that if not changed they will generate errors). mydomain and myhostname are examples. - the documentation provided with the source code (and installed by default) is not provided with the package I know that the Postfix is intended to run "out of the box" using sensible default configuration parameters (which do not need to be explicitly defined), requiring little more than a FQDN and working DNS. The software is also designed to be safe/secure (not allowing relaying of mails). For experienced users seeing what to change is not a problem, but it seems that this is not helpful for users new to the software. Not providing the package's own documentation (although man pages are included) is unhelpful. I understand that the quality of the software provided in RPM packages varies greatly, but these points above made me wonder if there is a list of general packaging guidelines. This at least allows users of the OpenPKG rpms to be aware that certain things should always be checked before even trying to start the software they've just installed. I'd like to help address the specific Postfix issues I've seen (which should be trivial), but want to make sure that I'm not overlooking something. Regards, Simon Mudd [1] Based on comments on the Postfix-users mailing list. [2] I believe that RedHat policy is to explicitly configure all network services this way ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
