diff options
author | 2013-07-08 13:26:14 -0500 | |
---|---|---|
committer | 2013-07-08 13:26:14 -0500 | |
commit | 0bd71cd8a16b54c9392afa30821e578315d53807 (patch) | |
tree | 930476fb73107d4955a9038ef61b7e6e3658339c /man | |
parent | equery: respect PORTAGE_CONFIGROOT too (diff) | |
download | gentoolkit-0bd71cd8a16b54c9392afa30821e578315d53807.tar.gz gentoolkit-0bd71cd8a16b54c9392afa30821e578315d53807.tar.bz2 gentoolkit-0bd71cd8a16b54c9392afa30821e578315d53807.zip |
Rename eclean --destructive option to --deep (Bug #475808)
This is a cosmetic change only. --destructive is still accepted for
backwards compatibility. Additionally, options array still refers to
the option as destrcutive.
Diffstat (limited to 'man')
-rw-r--r-- | man/eclean.1 | 14 |
1 files changed, 7 insertions, 7 deletions
diff --git a/man/eclean.1 b/man/eclean.1 index a6bad31..4267047 100644 --- a/man/eclean.1 +++ b/man/eclean.1 @@ -23,7 +23,7 @@ without recompiling it. Sure, it's also a mode in which your DISTDIR and PKGDIR stay rather big (although still not growing infinitely). For the 'distfiles', this mode is also quite slow because it requiries some access to the whole Portage tree. .PP -If you use the \-\-destructive option, eclean will only protect files corresponding to +If you use the \-\-deep option, eclean will only protect files corresponding to some currently installed package (taking their exact version into account). It will save much more space, while still preserving sources files around for minor revision bumps, and binaries for reinstallation of corrupted packages. But it won't keep files @@ -31,7 +31,7 @@ for less usual operations like downgrading or reinstalling an unmerged package. is also the fastest execution mode (big difference for distfiles), and the one used by most other cleaning scripts around like yacleaner (at least in its version 0.3). .PP -Somewhere in the middle, adding the \-\-package\-names option when using \-\-destructive +Somewhere in the middle, adding the \-\-package\-names option when using \-\-deep will protect files corresponding to all existing versions of installed packages. It will allow easy downgrading without recompilation or redownloading in case of trouble, but won't protect you against package uninstallation. @@ -53,7 +53,7 @@ Finally, you can list some categories or package names to protect in exclusion f .TP \fB\-C, \-\-nocolor\fP turn off colors on output .TP -\fB\-d, \-\-destructive\fP only keep the minimum for a reinstallation +\fB\-d, \-\-deep\fP only keep the minimum for a reinstallation .TP \fB\-e, \-\-exclude\-file=<path>\fP path to the exclusion file \fB<path>\fP is the absolute path to the exclusion file you want to use. @@ -63,7 +63,7 @@ you want to temporary ignore it. .TP \fB\-i, \-\-interactive\fP ask confirmation before deleting .TP -\fB\-n, \-\-package\-names\fP protect all versions (\-\-destructive only) +\fB\-n, \-\-package\-names\fP protect all versions (\-\-deep only) .TP \fB\-p, \-\-pretend\fP only display what would be cleaned .TP @@ -97,7 +97,7 @@ FEATURES flags. command\-line. .SS "Options for the 'distfiles' action" .TP -\fB\-f, \-\-fetch\-restricted\fP protect fetch\-restricted files (\-\-destructive only) +\fB\-f, \-\-fetch\-restricted\fP protect fetch\-restricted files (\-\-deep only) .TP \fB\-s, \-\-size\-limit=<size>\fP don't delete distfiles bigger than <size> <size> is a size specification: "10M" is "ten megabytes", "200K" is "two hundreds kilobytes", @@ -161,7 +161,7 @@ are less than one month old, bigger than 50MB, or fetch\-restricted: .br .B # eclean\-dist \-d \-t1m \-s50M \-f .LP -From a crontab, silently clean packages in the safest mode, and then distfiles in destructive +From a crontab, silently clean packages in the safest mode, and then distfiles in deep mode but protecting files less than a week old, every sunday at 1am: .br .B 0 1 * * sun \ \ eclean \-C \-q packages ; eclean \-C \-q \-d \-t1w distfiles @@ -172,7 +172,7 @@ While running and searching distfiles for cleaning, elcean will report any unava .".TP ."The policy used to decide if a distfile can be removed or not relies on the SRC_URI variables ."of ebuilds. It means that if an ebuild uses files that are not part of its SRC_URI, eclean will ."probably remove them. This are ebuilds bugs, please report them as such on ."http://bugs.gentoo.org. .".TP -."In safest mode (default, without the \-\-destructive option), this script can be very slow. There +."In safest mode (default, without the \-\-deep option), this script can be very slow. There ."is not much to do about it without hacking outside of the portage API. .SH "SEE ALSO" .TP |