Users should always be using a complete copy of the ports tree.
csup is leaving us shortly so don't bother mentioning it. Approved by: bcr (mentor)
This commit is contained in:
parent
b906641de3
commit
dbbb4ec933
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=39860
1 changed files with 1 additions and 27 deletions
|
@ -4088,38 +4088,12 @@ kern.timecounter.hardware: TSC -> i8254</screen>
|
|||
</question>
|
||||
|
||||
<answer>
|
||||
<para>First, always make sure that you have a completely
|
||||
<para>First, always make sure that you have a complete
|
||||
up-to-date Ports Collection. Errors that affect building
|
||||
<filename>INDEX</filename> from an up-to-date copy of the
|
||||
Ports Collection are high-visibility and are thus almost
|
||||
always fixed immediately.</para>
|
||||
|
||||
<para>However, if you are up-to-date, perhaps you are seeing
|
||||
another problem. <command>make <maketarget>index</maketarget></command>
|
||||
has a known bug in dealing with incomplete copies of the
|
||||
Ports Collection. It assumes that you have a local copy of
|
||||
every single port that every other port that you have a
|
||||
local copy of depends on. To explain, if you have a copy of
|
||||
<filename>foo/bar</filename> on your disk, and
|
||||
<filename>foo/bar</filename> depends on
|
||||
<filename>baz/quux</filename>, then you must also have a
|
||||
copy of <filename>baz/quux</filename> on your disk, and the
|
||||
ports <filename>baz/quux</filename> depends on, and so on.
|
||||
Otherwise, <command>make <maketarget>index</maketarget></command>
|
||||
has insufficient information to create its dependency
|
||||
tree.</para>
|
||||
|
||||
<para>This is particularly a problem for &os; users who
|
||||
utilize &man.csup.1; to track the Ports
|
||||
Collection but choose not to install certain categories by
|
||||
specifying them in <filename>refuse</filename>. In theory,
|
||||
one should be able to refuse categories, but in practice
|
||||
there are too many ports that depend on ports in other
|
||||
categories. Until someone comes up with a solution for this
|
||||
problem, the general rule is that if you want to build
|
||||
<filename>INDEX</filename>, you must have a complete copy of
|
||||
the Ports Collection.</para>
|
||||
|
||||
<para>There are rare cases where <filename>INDEX</filename>
|
||||
will not build due to odd cases involving
|
||||
<makevar>WITH_<replaceable>*</replaceable></makevar> or
|
||||
|
|
Loading…
Reference in a new issue