aboutsummaryrefslogtreecommitdiff
path: root/documentation/content/en/books/porters-handbook/upgrading/_index.adoc
diff options
context:
space:
mode:
Diffstat (limited to 'documentation/content/en/books/porters-handbook/upgrading/_index.adoc')
-rw-r--r--documentation/content/en/books/porters-handbook/upgrading/_index.adoc18
1 files changed, 5 insertions, 13 deletions
diff --git a/documentation/content/en/books/porters-handbook/upgrading/_index.adoc b/documentation/content/en/books/porters-handbook/upgrading/_index.adoc
index 3cd5e01f68..6978f0577c 100644
--- a/documentation/content/en/books/porters-handbook/upgrading/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/upgrading/_index.adoc
@@ -6,7 +6,7 @@ description: Upgrading a FreeBSD Port
tags: ["upgrading", "port", "git"]
showBookMenu: true
weight: 11
-path: "/books/porters-handbook/"
+path: "/books/porters-handbook/upgrading/"
---
[[port-upgrading]]
@@ -51,7 +51,7 @@ When a port is not the most recent version available from the authors, update th
The port might have already been updated to the new version.
When working with more than a few ports, it will probably be easier to use Git to keep the whole ports collection up-to-date,
-as described in the extref:{handbook}[Handbook, ports-using].
+as described in extref:{handbook}ports[Using the Ports Collection, ports-using].
This will have the added benefit of tracking all the port's dependencies.
The next step is to see if there is an update already pending.
@@ -59,16 +59,6 @@ To do this, there are two options.
There is a searchable interface to the https://bugs.freebsd.org/search/[FreeBSD Problem Report (PR) or bug database].
Select `Ports & Packages` in the `Product` multiple select menu, and enter the name of the port in the `Summary` field.
-However, sometimes people forget to put the name of the port into the Summary field in an unambiguous fashion.
-In that case, try searching in the `Comment` field in the `Detailled Bug Information` section, or try the crossref:keeping-up[portsmon,FreeBSD Ports Monitoring System] (also known as `portsmon`).
-This system attempts to classify port PRs by portname.
-To search for PRs about a particular port, use the http://portsmon.FreeBSD.org/portoverview.py[Overview of One Port].
-
-[NOTE]
-======
-The FreeBSD Ports Monitoring System (portsmon) is currently not working due to latest Python updates.
-======
-
If there is no pending PR, the next step is to send an email to the port's maintainer, as shown by `make maintainer`.
That person may already be working on an upgrade, or have a reason to not upgrade the port right now (because of, for example, stability problems of the new version), and there is no need to duplicate their work.
Note that unmaintained ports are listed with a maintainer of `ports@FreeBSD.org`, which is just the general ports mailing list, so sending mail there probably will not help in this case.
@@ -102,7 +92,7 @@ FreeBSD has over 4000 ports without maintainers, and this is an area where more
(For a detailed description of the responsibilities of maintainers, refer to the section in the extref:{developers-handbook}[Developer's Handbook, POLICIES-MAINTAINER].)
To submit the diff, use the https://bugs.freebsd.org/submit/[bug submit form] (product `Ports & Packages`, component `Individual Port(s)`).
-Always include the category with the port name, followed by colon, and brief descripton of the issue.
+Always include the category with the port name, followed by colon, and brief description of the issue.
Examples: `_category/portname_: _add FOO option_`; `_category/portname_: _Update to X.Y_`.
Please mention any added or deleted files in the message, as they have to be explicitly specified to man:git[1] when doing a commit.
Do not compress or encode the diff.
@@ -159,6 +149,8 @@ If adding, moving, or removing a file, use `git` to track these changes:
Make sure to check the port using the checklist in crossref:quick-porting[porting-testing,Testing the Port] and crossref:quick-porting[porting-portlint,Checking the Port with `portlint`].
+Also, update the checksum reference in distinfo with `make makesum`.
+
Before making the patch, fetch the latest repository and rebase the changes on top of it.
Watch and follow the output carefully.
If any of the files failed to rebase, it means that the upstream files changed while you were editing the same file, and the conflicts need to be resolved manually.