Add a warning about always updating the ports-base subcollection

whenever any part of the Ports Collection is updated to the CVSup
chapter of the Handbook.

Add a similar Q&A to the 'User Applications' section of the FAQ,
with the answer referencing the warning in the Handbook.

Reviewed by:	keramida
Approved by:	ceri (mentor), keramida, Stijn Hoop <stijn@win.tue.nl>
This commit is contained in:
Peter Pentchev 2003-02-19 07:25:18 +00:00
parent 925ae453aa
commit 9ad4236250
Notes: svn2git 2020-12-08 03:00:23 +00:00
svn path=/head/; revision=16071
2 changed files with 54 additions and 2 deletions

View file

@ -5178,6 +5178,26 @@ crw-rw-rw- 1 root wheel 41, 1 Oct 15 22:14 spx</screen>
connection.</para>
</answer>
</qandaentry>
<qandaentry>
<question id="ports-base-update">
<para>I updated parts of the Ports Collection using CVSup, and
now many ports fail to build with mysterious error messages!
What happened? Is the Ports Collection broken in some major
way?</para>
</question>
<answer>
<para>If you only update parts of the Ports Collection, using
one of its CVSup subcollections and not the
<literal>ports-all</literal> CVSup collection, you should
<emphasis>always</emphasis> update the
<literal>ports-base</literal> subcollection too! The reasons
are described <ulink
url="../handbook/cvsup.html#CVSUP-COLLEC-PBASE-WARN">in the
Handbook</ulink>.</para>
</answer>
</qandaentry>
</qandaset>
</chapter>

View file

@ -2526,6 +2526,26 @@ doc/zh_TW.Big5</screen>
<listitem>
<para>The FreeBSD Ports Collection.</para>
<important id="cvsup-collec-pbase-warn">
<para>If you do not want to update the whole of
<literal>ports-all</literal> (the whole ports tree),
but use one of the subcollections listed below,
make sure that you <emphasis>always</emphasis> update
the <literal>ports-base</literal> subcollection!
Whenever something changes in the ports build
infrastructure represented by
<literal>ports-base</literal>, it is virtually certain
that those changes will be used by <quote>real</quote>
ports real soon. Thus, if you only update the
<quote>real</quote> ports and they use some of the new
features, there is a very high chance that their build
will fail with some mysterious error message. The
<emphasis>very first</emphasis> thing to do in this
case is to make sure that your
<literal>ports-base</literal> subcollection is up to
date.</para>
</important>
<variablelist>
<varlistentry>
<term><literal>ports-archivers
@ -2559,8 +2579,20 @@ doc/zh_TW.Big5</screen>
release=cvs</literal></term>
<listitem>
<para>Miscellaneous files at the top of
/usr/ports.</para>
<para>The Ports Collection build infrastructure -
various files located in the
<filename>Mk/</filename> and
<filename>Tools/</filename> subdirectories of
<filename>/usr/ports</filename>.</para>
<note>
<para>Please see the <link
linkend="cvsup-collec-pbase-warn">important
warning above</link>: you should
<emphasis>always</emphasis> update this
subcollection, whenever you update any part of
the FreeBSD Ports Collection!</para>
</note>
</listitem>
</varlistentry>