[Bug 288040] Porter's Handbook § 13.14 .2 ambiguous, conflates two ideas

From: <bugzilla-noreply_at_freebsd.org>
Date: Sat, 05 Jul 2025 22:27:49 UTC
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=288040

            Bug ID: 288040
           Summary: Porter's Handbook § 13.14.2 ambiguous, conflates two
                    ideas
           Product: Documentation
           Version: Latest
          Hardware: Any
                OS: Any
            Status: New
          Severity: Affects Many People
          Priority: ---
         Component: Books & Articles
          Assignee: doc@FreeBSD.org
          Reporter: milios@ccsys.com

please forgive me for being pedantic; i am not entirely certain but what i
always understood was:

13.14.2. Marking a [Package] as Architecture Neutral
                            - or -
13.14.2. Marking a Port as [Producing Only Architecture-Neutral Artifacts]

Ports that do not [install any architecture-dependent files nor place any such
requirements upon end-user machine architecture] are identified by setting
NO_ARCH=yes.

Packages built from such ports...(remainder of subsection is good)


For your convenience, the current text:
                                                                            
------
13.14.2. Marking a Port as Architecture Neutral

Ports(*) that do not have any architecture-dependent files or requirements are
identified by setting NO_ARCH=yes.

Packages built from such ports have their architecture string ending in :*
(wildcard architecture) as opposed to, for example, freebsd:13:x86:64 (amd64
architecture).

(i) Note:
  NO_ARCH is meant to indicate that there is no need to build a package for
each
  of the supported architectures. The goal is to reduce the amount of resources
  spent on building and distributing the packages such as network bandwidth and
  disk space on mirrors and on distribution media. Currently, however, our
package
  infrastructure (e.g., package managers, mirrors, and package builders) is not
  set up to fully benefit from NO_ARCH.
------

(*) as i reach that word as written there it imparts to me the sense of that
journey DISTFILES -> .CURDIR -> WRKSRC, which i don't believe the writer
intended. Most ports are neutral in that regard, after all; such is why we love
open source. To me, it doesn't unmistakably impart the intended concept of
WRKDIR -> STAGEDIR -> PACKAGES -> [most crucially] PREFIX

-- 
You are receiving this mail because:
You are the assignee for the bug.