|author||Thomas De Schampheleire <firstname.lastname@example.org>||2013-12-07 09:16:47 (GMT)|
|committer||Peter Korsgaard <email@example.com>||2013-12-08 18:41:54 (GMT)|
manual: remove package clean commands
Signed-off-by: Thomas De Schampheleire <firstname.lastname@example.org> Signed-off-by: Peter Korsgaard <email@example.com>
5 files changed, 1 insertions, 13 deletions
diff --git a/docs/manual/adding-packages-autotools.txt b/docs/manual/adding-packages-autotools.txt
index 27991b2..d0c92ff 100644
@@ -145,9 +145,6 @@ cases, typical packages will therefore only use a few of them.
value is correct for most autotools packages, but it is still possible
to override it if needed.
-* +LIBFOO_CLEAN_OPT+ contains the make options used to
- clean the package. By default, the value is +clean+.
With the autotools infrastructure, all the steps required to build
and install the packages are already defined, and they generally work
well for most autotools-based packages. However, when required, it is
diff --git a/docs/manual/adding-packages-cmake.txt b/docs/manual/adding-packages-cmake.txt
index 4373423..29f2b8f 100644
@@ -126,9 +126,6 @@ typical packages will therefore only use a few of them.
for most CMake packages, but it is still possible to override it if
-* +LIBFOO_CLEAN_OPT+ contains the make options used to clean the
- package. By default, the value is +clean+.
With the CMake infrastructure, all the steps required to build and
install the packages are already defined, and they generally work well
for most CMake-based packages. However, when required, it is still
diff --git a/docs/manual/adding-packages-directory.txt b/docs/manual/adding-packages-directory.txt
index 700ec4f..36b7093 100644
@@ -269,7 +269,7 @@ different way, using different infrastructures:
These are based on an infrastructure similar to the one used for
autotools-based packages, but require a little more work from the
developer. They specify what should be done for the configuration,
- compilation, installation and cleanup of the package. This
+ compilation and installation of the package. This
infrastructure must be used for all packages that do not use the
autotools as their build system. In the future, other specialized
infrastructures might be written for other build systems. We cover
diff --git a/docs/manual/adding-packages-generic.txt b/docs/manual/adding-packages-generic.txt
index 7ff0a61..14971b5 100644
@@ -413,9 +413,6 @@ different steps of the build process.
should be installed, since they might be needed to compile other
-* +LIBFOO_CLEAN_CMDS+, lists the actions to perform to clean up
- the build directory of the package.
* +LIBFOO_INSTALL_INIT_SYSV+ and +LIBFOO_INSTALL_INIT_SYSTEMD+ list the
actions to install init scripts either for the systemV-like init systems
(busybox, sysvinit, etc.) or for the systemd units. These commands
diff --git a/docs/manual/package-make-target.txt b/docs/manual/package-make-target.txt
index 8210e94..9eefe68 100644
@@ -63,9 +63,6 @@ Additionally, there are some other useful make targets:
| +show-depends+ | Displays the dependencies required to build the
-| +clean+ | Run the clean command of the package; _note that
- this is not implemented for all packages_
| +dirclean+ | Remove the whole package build directory
| +rebuild+ | Re-run the compilation commands - this only makes