Differential D35025 Diff 105332 documentation/content/en/books/porters-handbook/upgrading/_index.adoc
Changeset View
Changeset View
Standalone View
Standalone View
documentation/content/en/books/porters-handbook/upgrading/_index.adoc
Show First 20 Lines • Show All 53 Lines • ▼ Show 20 Lines | |||||
as described in the extref:{handbook}[Handbook, ports-using]. | as described in the extref:{handbook}[Handbook, ports-using]. | ||||
This will have the added benefit of tracking all the port's dependencies. | 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. | The next step is to see if there is an update already pending. | ||||
To do this, there are two options. | 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]. | 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. | 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`. | 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. | 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. | 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. | ||||
If the maintainer asks you to do the upgrade or there is no maintainer, then help out FreeBSD by preparing the update! Please do this by using the man:diff[1] command in the base system. | If the maintainer asks you to do the upgrade or there is no maintainer, then help out FreeBSD by preparing the update! Please do this by using the man:diff[1] command in the base system. | ||||
To create a suitable `diff` for a single patch, copy the file that needs patching to [.filename]#something.orig#, save the changes to [.filename]#something# and then create the patch: | To create a suitable `diff` for a single patch, copy the file that needs patching to [.filename]#something.orig#, save the changes to [.filename]#something# and then create the patch: | ||||
▲ Show 20 Lines • Show All 221 Lines • Show Last 20 Lines |