git: 6c87ece22b - main - [phb]: Changes to MAINTAINER require bump of PORTREVISION

From: Fernando Apesteguía <>
Date: Mon, 08 May 2023 10:12:28 UTC
The branch main has been updated by fernape:


commit 6c87ece22b65be5419040deb58f578dbc39ffe6b
Author:     Fernando Apesteguía <>
AuthorDate: 2023-05-04 14:23:02 +0000
Commit:     Fernando Apesteguía <>
CommitDate: 2023-05-08 10:07:02 +0000

    [phb]: Changes to MAINTAINER require bump of PORTREVISION
    As discussed in the mail list since users would like to know who to contact in
    case of problems. It also helps in reproducible builds.
    Reviewed by:            manu@
    Differential Revision:
 documentation/content/en/books/porters-handbook/makefiles/_index.adoc | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/documentation/content/en/books/porters-handbook/makefiles/_index.adoc b/documentation/content/en/books/porters-handbook/makefiles/_index.adoc
index 4424c368d0..ac8a9a5f51 100644
--- a/documentation/content/en/books/porters-handbook/makefiles/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/makefiles/_index.adoc
@@ -299,6 +299,7 @@ Examples of when `PORTREVISION` must be bumped:
 * Changes in the packing list or the install-time behavior of the package. For example, a change to a script which generates initial data for the package, like man:ssh[1] host keys.
 * Version bump of a port's shared library dependency (in this case, someone trying to install the old package after installing a newer version of the dependency will fail since it will look for the old libfoo.x instead of libfoo.(x+1)).
 * Silent changes to the port distfile which have significant functional differences. For example, changes to the distfile requiring a correction to [.filename]#distinfo# with no corresponding change to `DISTVERSION`, where a `diff -ru` of the old and new versions shows non-trivial changes to the code.
+* Changes to `MAINTAINER`.
 Examples of changes which do not require a `PORTREVISION` bump:
@@ -306,7 +307,6 @@ Examples of changes which do not require a `PORTREVISION` bump:
 * Changes to `MASTER_SITES` or other functional changes to the port which do not affect the resulting package.
 * Trivial patches to the distfile such as correction of typos, which are not important enough that users of the package have to go to the trouble of upgrading.
 * Build fixes which cause a package to become compilable where it was previously failing. As long as the changes do not introduce any functional change on any other platforms on which the port did previously build. Since `PORTREVISION` reflects the content of the package, if the package was not previously buildable then there is no need to increase `PORTREVISION` to mark a change.
-* Changes to `MAINTAINER`.
 A rule of thumb is to decide whether a change committed to a port is something which _some_ people would benefit from having.
 Either because of an enhancement, fix, or by virtue that the new package will actually work at all.