Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

create qmail-release in /var/qmail/control #268

Open
mbhangui opened this issue Feb 10, 2024 · 0 comments
Open

create qmail-release in /var/qmail/control #268

mbhangui opened this issue Feb 10, 2024 · 0 comments
Assignees
Labels
build enhancement New feature or request

Comments

@mbhangui
Copy link
Contributor

mbhangui commented Feb 10, 2024

There is some merit in creating a release file (/var/qmail/control/qmail-release) with the following information

  1. Version number
  2. build information like if was built from source or installed from RPM/Debain/pkgsrc, etc
  3. support url, IRC url, documentation url, etc
  4. C compiler and version and the OS version used for building the binaries

Often it happens that some admin installs qmail, netqmail, s/qmail, indimail-mta, notqmail. Then the admin leaves the company. When some issue happens, the next admin has to figure out how to solve the issue and where to ask for help. When the admin asks for help, we can ask the admin to print the content of the release file. This information can quickly tells is if there was a bug (that the admin is now facing) that was solved in the later release. It is a good practice to record information about the build (most important being the version number). The Makefile setup target can create this file. Binary packaging can also create this file.

qmail-showctl can be modifed to show this information

A sample release file for notmail can be like this

NAME=notqmail
Description="notqmail"
MTA_version=1.09
ID=notqmail
HOME_URL="https://github.com/notqmail/notqmail"
IRC="#qmail"
Documentation="https://notqmail.org/"
PACKAGE_BUGREPORT="'notqmail <support@notqmail.org>"
@mbhangui mbhangui added enhancement New feature or request build labels Feb 10, 2024
@mbhangui mbhangui self-assigned this Feb 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
build enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant