-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`:
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 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 @@
[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 @@
[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
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