Note that NO_ARCH is not fully utilized by our infrastructure yet

1 files changed, 12 insertions, 0 deletions

diff --git a/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml b/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
index 2719f12388..ec892a89b0 100644
--- a/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
+++ b/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
@@ -546,6 +546,18 @@ cc -o someprogram source1.o source2.o -L/usr/local/lib -lsomelib</programlisting
       <para>Ports that do not have any architecture-dependent files
         or requirements are identified by setting
         <literal>NO_ARCH=yes</literal>.</para>
+
+      <note>
+        <para><literal>NO_ARCH</literal> 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
+          <literal>NO_ARCH</literal>.</para>
+      </note>
     </sect2>
 
     <sect2 xml:id="dads-arch-ignore">