Page MenuHomeFreeBSD
Files F144014954

D50471.id.diff
No OneTemporary
Actions

D50471.id.diff
View Options

diff --git a/documentation/content/en/articles/committers-guide/_index.adoc b/documentation/content/en/articles/committers-guide/_index.adoc
--- a/documentation/content/en/articles/committers-guide/_index.adoc
+++ b/documentation/content/en/articles/committers-guide/_index.adoc
@@ -3167,7 +3167,7 @@
. Test your changes before committing them.
+
If your changes are to the kernel, make sure you can still compile both GENERIC and LINT.
-If your changes are anywhere else, make sure you can still make world.
+If your changes are anywhere else, make sure you can still compile userspace via `make buildworld`.
If your changes are to a branch, make sure your testing occurs with a machine which is running that code.
If you have a change which also may break another architecture, be sure and test on all supported architectures.
Please ensure your change works for
diff --git a/documentation/content/en/books/developers-handbook/policies/_index.adoc b/documentation/content/en/books/developers-handbook/policies/_index.adoc
--- a/documentation/content/en/books/developers-handbook/policies/_index.adoc
+++ b/documentation/content/en/books/developers-handbook/policies/_index.adoc
@@ -133,7 +133,7 @@
.. The _Release Engineer_ decides whether or not it goes into the release.
. User-land files:
-.. The link:https://www.FreeBSD.org/administration/#t-core[Core team] decides if the code should be part of `make world`.
+.. The link:https://www.FreeBSD.org/administration/#t-core[Core team] decides if the code should be part of the installed base system.
.. The link:https://www.FreeBSD.org/administration/#t-re[Release Engineering] decides if it goes into the release.
[[policies-shlib]]
diff --git a/documentation/content/en/books/developers-handbook/tools/_index.adoc b/documentation/content/en/books/developers-handbook/tools/_index.adoc
--- a/documentation/content/en/books/developers-handbook/tools/_index.adoc
+++ b/documentation/content/en/books/developers-handbook/tools/_index.adoc
@@ -530,7 +530,7 @@
So, when you type `make`, it will make sure that [.filename]#foo# is up to date with respect to your latest changes to [.filename]#foo.c#.
This principle can be extended to [.filename]#Makefile#'s with hundreds of targets-in fact, on FreeBSD,
-it is possible to compile the entire operating system just by typing `make world` in the appropriate directory!
+it is possible to compile the entire operating system just by typing `make buildworld` at the top level directory in the src tree.
Another useful property of makefiles is that the targets do not have to be programs.
For instance, we could have a make file that looks like this:

File Metadata

Mime Type
text/plain
Expires
Wed, Feb 4, 9:58 AM (7 h, 41 m)
Storage Engine
blob
Storage Format
Raw Data
Storage Handle
28433655
Default Alt Text
D50471.id.diff (2 KB)

Event Timeline