aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAlexander Ziaee <ziaee@FreeBSD.org>2026-09-06 12:45:29 +0000
committerAlexander Ziaee <ziaee@FreeBSD.org>2026-09-06 12:55:19 +0000
commit7ef5bfd0ff80ba3ff3e72f679efbd244208340af (patch)
treea60b1e8a551b57e6b325b7920fe9e446ec325005
parent565dd337b0af16274b8fcf11294980e2f39e5680 (diff)
contributing: Clean up i386 maintainer expectaions
Discussed with: fuz Reported by: Bohdan Artiushenko Event: Berlin Hackathon 202609 Closes: https://github.com/freebsd/freebsd-doc/pull/707
-rw-r--r--documentation/content/en/articles/contributing/_index.adoc13
1 files changed, 3 insertions, 10 deletions
diff --git a/documentation/content/en/articles/contributing/_index.adoc b/documentation/content/en/articles/contributing/_index.adoc
index 85e398d4f5..ee4c022771 100644
--- a/documentation/content/en/articles/contributing/_index.adoc
+++ b/documentation/content/en/articles/contributing/_index.adoc
@@ -454,18 +454,11 @@ That is it!
This section is about discovering and fixing problems that stop your ports from building correctly.
-FreeBSD only guarantees that the Ports Collection works on the `-STABLE` branches.
-In theory, you should be able to get by with running the latest release of each stable branch (since the ABIs are not supposed to change) but if you can run the branch, that is even better.
-
-Since the majority of FreeBSD installations run on PC-compatible machines (what is termed the `i386` architecture), we expect you to keep the port working on that architecture.
-We prefer that ports also work on the `amd64` architecture running native.
+We expect you to keep the port working on `amd64` and preferably `aarch64`.
It is completely fair to ask for help if you do not have one of these machines.
-[NOTE]
-====
-The usual failure modes for non-`x86` machines are that the original programmers assumed that, for instance, pointers are `int`-s, or that a relatively lax older gcc compiler was being used.
-More and more, application authors are reworking their code to remove these assumptions - but if the author is not actively maintaining their code, you may need to do this yourself.
-====
+FreeBSD only guarantees that the Ports Collection works on the `-STABLE` branches.
+In theory, you should be able to get by with running the latest release of each stable branch (since the ABIs are not supposed to change) but if you can run the branch, that is even better.
These are the tasks you need to perform to ensure your port is able to be built: