Add a blurb about the main reason for not including CVSup in the base
system: the fact that we would need a Modula-3 compiler to go with it. PR: 70124 Suggested by: Joel Dahl <joel@automatvapen.se>
This commit is contained in:
parent
e323638302
commit
47dceec768
Notes:
svn2git
2020-12-08 03:00:23 +00:00
svn path=/head/; revision=21910
1 changed files with 24 additions and 0 deletions
|
@ -5059,6 +5059,30 @@ kern.timecounter.hardware: TSC -> i8254</screen>
|
|||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="cvsup-in-base">
|
||||
<para>Why is CVSup not integrated in the main FreeBSD tree?
|
||||
</para>
|
||||
</question>
|
||||
|
||||
<answer>
|
||||
<para>The FreeBSD base system is designed as self-hosting - it
|
||||
should be possible to build the whole operating system starting
|
||||
with a very limited set of tools. Thus, the actual build tools
|
||||
needed to compile the FreeBSD sources are bundled with the
|
||||
sources themselves. This includes a C compiler (&man.gcc.1;),
|
||||
&man.make.1;, &man.awk.1;, and similar tools.</para>
|
||||
|
||||
<para>Since CVSup is written in Modula-3, adding it to the FreeBSD
|
||||
base system would also require adding and maintaining a Modula-3
|
||||
compiler. This would lead to both a growth in the disk space
|
||||
consumed by the FreeBSD sources and additional maintenance work.
|
||||
Thus, it is much easier for both the developers and users to
|
||||
keep CVSup as a separate port, which can be easily installed as
|
||||
a package bundled on the FreeBSD installation CD's.</para>
|
||||
</answer>
|
||||
</qandaentry>
|
||||
|
||||
<qandaentry>
|
||||
<question id="ports-update">
|
||||
<para>I updated the sources, now how do I update my installed
|
||||
|
|
Loading…
Reference in a new issue