[pkgsrc/trunk]: pkgsrc/doc/guide/files Instruct the reader to set prefer-pkgs...

[sevan <sevan%pkgsrc.org@localhost>]

details:   https://anonhg.NetBSD.org/pkgsrc/rev/4f9400dc0fe6
branches:  trunk
changeset: 356877:4f9400dc0fe6
user:      sevan <sevan%pkgsrc.org@localhost>
date:      Fri Jan 06 20:26:39 2017 +0000

description:
Instruct the reader to set prefer-pkgsrc during bootstrap. It appears that
setting this post bootstrap does create issues, as observed with a Linux user
today.

diffstat:

 doc/guide/files/buildlink.xml |  13 ++++++++++++-
 1 files changed, 12 insertions(+), 1 deletions(-)

diffs (27 lines):

diff -r 4a85299625d0 -r 4f9400dc0fe6 doc/guide/files/buildlink.xml
--- a/doc/guide/files/buildlink.xml     Fri Jan 06 10:59:05 2017 +0000
+++ b/doc/guide/files/buildlink.xml     Fri Jan 06 20:26:39 2017 +0000
@@ -1,4 +1,4 @@
-<!-- $NetBSD: buildlink.xml,v 1.39 2016/07/10 07:46:29 rillig Exp $ -->
+<!-- $NetBSD: buildlink.xml,v 1.40 2017/01/06 20:26:39 sevan Exp $ -->
 
 <chapter id="buildlink">
   <title>Buildlink methodology</title>
@@ -587,6 +587,17 @@
       <filename>builtin.mk</filename>
       file to be listed in <varname>PREFER_NATIVE</varname>,
       otherwise it is simply ignored in that list.</para>
+
+      <para>Setting <varname>PREFER_NATIVE</varname> should be performed
+      straight after bootstrap and <varname>PREFER_PKGSRC</varname> during
+      bootstrap.
+      Switching between settings globally at a later date can introduce
+      complications with dependency resolution. This is caused by packages
+      built with the opposite preference being installed alongside each other.</para>
+      
+<screen>
+&rprompt; <userinput>./bootstrap --prefer-pkgsrc yes</userinput>
+</screen>
     </sect2>
   </sect1>
 </chapter>