svn commit: r54671 - head/en_US.ISO8859-1/books/porters-handbook/porting-dads

Mateusz Piotrowski <[email protected]>
Newsgroups gmane.os.freebsd.devel.cvs.doc
Message-ID <[email protected]>
Author: 0mp
Date: Tue Nov  3 11:57:09 2020
New Revision: 54671
URL: https://svnweb.freebsd.org/changeset/doc/54671

Log:
  Note that NO_ARCH is not fully utilized by our infrastructure yet

Modified:
  head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml

Modified: head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml
==============================================================================
--- head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml	Mon Nov  2 22:19:48 2020	(r54670)
+++ head/en_US.ISO8859-1/books/porters-handbook/porting-dads/chapter.xml	Tue Nov  3 11:57:09 2020	(r54671)
@@ -546,6 +546,18 @@ cc -o someprogram source1.o source2.o -L/usr/local/lib
       <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">
_______________________________________________
[email protected] mailing list
https://lists.freebsd.org/mailman/listinfo/svn-doc-all
To unsubscribe, send any mail to "[email protected]"
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.