git: 890d271c6b - main - porters-handbook/testing: update to currently supported versions
- Go to: [ bottom of page ] [ top of archives ] [ this month ]
Date: Sun, 12 Oct 2025 03:46:11 UTC
The branch main has been updated by marck:
URL: https://cgit.FreeBSD.org/doc/commit/?id=890d271c6b527125476c6e279d27a48a8bfd472d
commit 890d271c6b527125476c6e279d27a48a8bfd472d
Author: Dmitry Morozovsky <marck@FreeBSD.org>
AuthorDate: 2025-10-11 16:42:06 +0000
Commit: Dmitry Morozovsky <marck@FreeBSD.org>
CommitDate: 2025-10-12 03:39:07 +0000
porters-handbook/testing: update to currently supported versions
stable/12 are gone, switch to stable/14 and last previous release in examples.
Reviewed by: maxim
Differential Revision: https://reviews.freebsd.org/D53040
---
.../en/books/porters-handbook/testing/_index.adoc | 84 +++++++++++-----------
1 file changed, 42 insertions(+), 42 deletions(-)
diff --git a/documentation/content/en/books/porters-handbook/testing/_index.adoc b/documentation/content/en/books/porters-handbook/testing/_index.adoc
index 4c94b4fc85..85433d1df0 100644
--- a/documentation/content/en/books/porters-handbook/testing/_index.adoc
+++ b/documentation/content/en/books/porters-handbook/testing/_index.adoc
@@ -293,41 +293,41 @@ Create the base jails which poudriere will use for building:
[source,shell]
....
-# poudriere jail -c -j 131Ramd64 -v 13.1-RELEASE -a amd64
+# poudriere jail -c -j 143Ramd64 -v 14.3-RELEASE -a amd64
....
-Fetch a `13.1-RELEASE` for `amd64` from the FTP server given by `FREEBSD_HOST` in [.filename]#poudriere.conf#,
-create the zfs file system `tank/poudriere/jails/131Ramd64`,
-mount it on [.filename]#/poudriere/jails/131Ramd64# and extract the `13.1-RELEASE` tarballs into this file system.
+Fetch a `14.3-RELEASE` for `amd64` from the HTTPS server given by `FREEBSD_HOST` in [.filename]#poudriere.conf#,
+create the zfs file system `tank/poudriere/jails/143Ramd64`,
+mount it on [.filename]#/poudriere/jails/143Ramd64# and extract the `14.3-RELEASE` tarballs into this file system.
[source,shell]
....
-# poudriere jail -c -j 12i386 -v stable/12 -a i386 -m git+https
+# poudriere jail -c -j 13i386 -v stable/13 -a i386 -m git+https
....
-Create `tank/poudriere/jails/12i386`, mount it on [.filename]#/poudriere/jails/12i386#,
-then check out the tip of the Git branch of `FreeBSD-12-STABLE` from `GIT_HOST` in [.filename]#poudriere.conf# or the default `git.freebsd.org` into [.filename]#/poudriere/jails/12i386/usr/src#,
-then complete a `buildworld` and install it into [.filename]#/poudriere/jails/12i386#.
+Create `tank/poudriere/jails/13i386`, mount it on [.filename]#/poudriere/jails/13i386#,
+then check out the tip of the Git branch of `FreeBSD-13-STABLE` from `GIT_HOST` in [.filename]#poudriere.conf# or the default `git.freebsd.org` into [.filename]#/poudriere/jails/13i386/usr/src#,
+then complete a `buildworld` and install it into [.filename]#/poudriere/jails/13i386#.
[NOTE]
====
While it is possible to build a newer version of FreeBSD on an older version, most of the time it will not run.
-For example, if a `stable/13` jail is needed, the host will have to run `stable/13` too.
-Running `13.1-RELEASE` is not enough.
+For example, if a `stable/14` jail is needed, the host will have to run `stable/14` too.
+Running `14.3-RELEASE` is not enough.
====
[NOTE]
====
-To create a poudriere jail for `14.0-CURRENT`:
+To create a poudriere jail for `16.0-CURRENT`:
[source,shell]
....
-# poudriere jail -c -j 14amd64 -v main -a amd64 -m git+https
+# poudriere jail -c -j 16amd64 -v main -a amd64 -m git+https
....
-In order to run a `14.0-CURRENT` poudriere jail the host must be running `14.0-CURRENT`.
+In order to run a `16.0-CURRENT` poudriere jail the host must be running `16.0-CURRENT`.
In general, newer kernels can build and run older jails.
-For instance, a `14.0-CURRENT` kernel can build and run a `12.4-STABLE` if the `COMPAT_FREEBSD12` kernel option was compiled in (on by default in `14.0-CURRENT`[.filename]#GENERIC# kernel config).
+For instance, a `16.0-CURRENT` kernel can build and run a `14.3-STABLE` if the `COMPAT_FREEBSD14` kernel option was compiled in (on by default in `16.0-CURRENT`[.filename]#GENERIC# kernel config).
====
A list of jails currently known to poudriere can be shown with `poudriere jail -l`:
@@ -336,8 +336,8 @@ A list of jails currently known to poudriere can be shown with `poudriere jail -
....
# poudriere jail -l
JAILNAME VERSION ARCH METHOD
-131Ramd64 13.1-RELEASE amd64 ftp
-12i386 12.4-STABLE i386 git+https
+143Ramd64 14.3-RELEASE amd64 http
+13i386 13.5-STABLE i386 git+https
....
[[testing-poudriere-maintaining-jails]]
@@ -385,7 +385,7 @@ Afterward it is included in the list of known ports trees:
....
# poudriere ports -l
PORTSTREE METHOD TIMESTAMP PATH
-default git+https 2020-07-20 04:23:56 /poudriere/ports/default
+default git+https 2025-07-20 04:23:56 /poudriere/ports/default
....
[NOTE]
@@ -416,7 +416,7 @@ This will be listed in the table of known trees:
....
# poudriere ports -l
PORTSTREE METHOD TIMESTAMP PATH
-development null 2020-07-20 05:06:33 /work/ports
+development null 2025-07-20 05:06:33 /work/ports
....
[NOTE]
@@ -448,11 +448,11 @@ crossref:testing[testing-poudriere-ports-tree-manual, Using Manually Managed Por
After jails and ports trees have been set up, the result of a contributor's modifications to the ports tree can be tested.
-For example, local modifications to the package:www/firefox[] port located in [.filename]#/work/ports/www/firefox# can be tested in the previously created 13.1-RELEASE jail:
+For example, local modifications to the package:www/firefox[] port located in [.filename]#/work/ports/www/firefox# can be tested in the previously created 14.3-RELEASE jail:
[source,shell]
....
-# poudriere testport -j 131Ramd64 -p development -o www/firefox
+# poudriere testport -j 143Ramd64 -p development -o www/firefox
....
This will build all dependencies of Firefox.
@@ -460,10 +460,10 @@ If a dependency has been built previously and is still up-to-date, the pre-built
If a dependency has no up-to-date package, one will be built with default options in a jail.
Then Firefox itself is built.
-The complete build of every port is logged to [.filename]#/poudriere/data/logs/bulk/131Ri386-development/build-time/logs#.
+The complete build of every port is logged to [.filename]#/poudriere/data/logs/bulk/143Ri386-development/build-time/logs#.
-The directory name `131Ri386-development` is derived from the arguments to `-j` and `-p`, respectively.
-For convenience, a symbolic link [.filename]#/poudriere/data/logs/bulk/131Ri386-development/latest# is also maintained.
+The directory name `143Ri386-development` is derived from the arguments to `-j` and `-p`, respectively.
+For convenience, a symbolic link [.filename]#/poudriere/data/logs/bulk/143Ri386-development/latest# is also maintained.
The link points to the latest _build-time_ directory.
Also in this directory is an [.filename]#index.html# for observing the build process with a web browser.
@@ -472,7 +472,7 @@ To ease investigation, jails can be kept running after the build by adding `-i`
[source,shell]
....
-# poudriere testport -j 131Ramd64 -p development -i -o www/firefox
+# poudriere testport -j 143Ramd64 -p development -i -o www/firefox
....
After the build completes, and regardless of whether it was successful, a shell is provided within the jail.
@@ -483,16 +483,16 @@ It is then possible to man:jexec[8] into it:
[source,shell]
....
-# poudriere testport -j 131Ramd64 -p development -I -o www/firefox
+# poudriere testport -j 143Ramd64 -p development -I -o www/firefox
[...]
====>> Installing local Pkg repository to /usr/local/etc/pkg/repos
-====>> Leaving jail 131Ramd64-development-n running, mounted at /poudriere/data/.m/131Ramd64-development/ref for interactive run testing
-====>> To enter jail: jexec 131Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root
-====>> To stop jail: poudriere jail -k -j 131Ramd64 -p development
-# jexec 131Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root
+====>> Leaving jail 143Ramd64-development-n running, mounted at /poudriere/data/.m/143Ramd64-development/ref for interactive run testing
+====>> To enter jail: jexec 143Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root
+====>> To stop jail: poudriere jail -k -j 143Ramd64 -p development
+# jexec 143Ramd64-development-n env -i TERM=$TERM /usr/bin/login -fp root
# [do some stuff in the jail]
# exit
-# poudriere jail -k -j 131Ramd64 -p development
+# poudriere jail -k -j 143Ramd64 -p development
====>> Umounting file systems
....
@@ -502,7 +502,7 @@ Adding the `-c`:
[source,shell]
....
-# poudriere testport -j 131Ramd64 -c -o www/firefox
+# poudriere testport -j 143Ramd64 -c -o www/firefox
....
Presents the port configuration dialog before the port is built.
@@ -531,17 +531,17 @@ For instance, testing package:www/firefox[] in a specific set named `devset`, ad
[source,shell]
....
-# poudriere testport -j 131Ramd64 -p development -z devset -o www/firefox
+# poudriere testport -j 143Ramd64 -p development -z devset -o www/firefox
....
This will look for the existence of these directories in this order:
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-development-devset-options#
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-devset-options#
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-development-options#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-development-devset-options#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-devset-options#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-development-options#
* [.filename]#/usr/local/etc/poudriere.d/devset-options#
* [.filename]#/usr/local/etc/poudriere.d/development-options#
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-options#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-options#
* [.filename]#/usr/local/etc/poudriere.d/options#
From this list, poudriere man:nullfs[5]-mounts the _first existing_ directory tree into the [.filename]#/var/db/ports# directory of the build jails.
@@ -575,7 +575,7 @@ For instance:
[source,shell]
....
-# poudriere testport -j 131Ramd64 -p development -z devset -o www/firefox
+# poudriere testport -j 143Ramd64 -p development -z devset -o www/firefox
....
causes poudriere to check for the existence of these files in this order:
@@ -583,14 +583,14 @@ causes poudriere to check for the existence of these files in this order:
* [.filename]#/usr/local/etc/poudriere.d/make.conf#
* [.filename]#/usr/local/etc/poudriere.d/devset-make.conf#
* [.filename]#/usr/local/etc/poudriere.d/development-make.conf#
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-make.conf#
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-development-make.conf#
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-devset-make.conf#
-* [.filename]#/usr/local/etc/poudriere.d/131Ramd64-development-devset-make.conf#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-make.conf#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-development-make.conf#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-devset-make.conf#
+* [.filename]#/usr/local/etc/poudriere.d/143Ramd64-development-devset-make.conf#
Unlike with sets, all of the found files will be appended, _in that order_, into one [.filename]#make.conf# inside the build jails.
It is hence possible to have general make variables, intended to affect all builds in [.filename]#/usr/local/etc/poudriere.d/make.conf#.
-Special variables, intended to affect only certain jails or sets can be set in specialised [.filename]#make.conf# files, such as [.filename]#/usr/local/etc/poudriere.d/131Ramd64-development-devset-make.conf#.
+Special variables, intended to affect only certain jails or sets can be set in specialised [.filename]#make.conf# files, such as [.filename]#/usr/local/etc/poudriere.d/143Ramd64-development-devset-make.conf#.
[[testing-poudriere-sets-perl]]
.Using [.filename]#make.conf# to Change Default Perl