Browse Source

manual: remove package clean commands

Signed-off-by: Thomas De Schampheleire <thomas.de.schampheleire@gmail.com>
Signed-off-by: Peter Korsgaard <peter@korsgaard.com>
Thomas De Schampheleire 11 years ago
parent
commit
436dc00d7a

+ 0 - 3
docs/manual/adding-packages-autotools.txt

@@ -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
   value is correct for most autotools packages, but it is still possible
   to override it if needed.
   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
 With the autotools infrastructure, all the steps required to build
 and install the packages are already defined, and they generally work
 and install the packages are already defined, and they generally work
 well for most autotools-based packages. However, when required, it is
 well for most autotools-based packages. However, when required, it is

+ 0 - 3
docs/manual/adding-packages-cmake.txt

@@ -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
   for most CMake packages, but it is still possible to override it if
   needed.
   needed.
 
 
-* +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
 With the CMake infrastructure, all the steps required to build and
 install the packages are already defined, and they generally work well
 install the packages are already defined, and they generally work well
 for most CMake-based packages. However, when required, it is still
 for most CMake-based packages. However, when required, it is still

+ 1 - 1
docs/manual/adding-packages-directory.txt

@@ -269,7 +269,7 @@ different way, using different infrastructures:
   These are based on an infrastructure similar to the one used for
   These are based on an infrastructure similar to the one used for
   autotools-based packages, but require a little more work from the
   autotools-based packages, but require a little more work from the
   developer. They specify what should be done for the configuration,
   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
   infrastructure must be used for all packages that do not use the
   autotools as their build system. In the future, other specialized
   autotools as their build system. In the future, other specialized
   infrastructures might be written for other build systems.  We cover
   infrastructures might be written for other build systems.  We cover

+ 0 - 3
docs/manual/adding-packages-generic.txt

@@ -413,9 +413,6 @@ different steps of the build process.
   should be installed, since they might be needed to compile other
   should be installed, since they might be needed to compile other
   packages.
   packages.
 
 
-* +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
 * +LIBFOO_INSTALL_INIT_SYSV+ and +LIBFOO_INSTALL_INIT_SYSTEMD+ list the
   actions to install init scripts either for the systemV-like init systems
   actions to install init scripts either for the systemV-like init systems
   (busybox, sysvinit, etc.) or for the systemd units. These commands
   (busybox, sysvinit, etc.) or for the systemd units. These commands

+ 0 - 3
docs/manual/package-make-target.txt

@@ -63,9 +63,6 @@ Additionally, there are some other useful make targets:
 | +show-depends+    | Displays the dependencies required to build the
 | +show-depends+    | Displays the dependencies required to build the
 package
 package
 
 
-| +clean+           | Run the clean command of the package; _note that
-  this is not implemented for all packages_
-
 | +dirclean+        | Remove the whole package build directory
 | +dirclean+        | Remove the whole package build directory
 
 
 | +rebuild+         | Re-run the compilation commands - this only makes
 | +rebuild+         | Re-run the compilation commands - this only makes