.TH "eclean" "1" "0.4.1" "gentoolkit-0.2.???" .SH "NAME" eclean \- A cleaning tool for Gentoo distfiles and binary packages. .SH "SYNOPSIS" .LP .B eclean \fR[\fIglobal\-options\fR] ... <\fIactions\fR> \fR[\fIaction\-options\fR] ... .LP .B eclean\-dist \fR[\fIglobal\-options, distfiles\-options\fR] ... .LP .B eclean\-pkg \fR[\fIglobal\-options, packages\-options\fR] ... .LP .B eclean(-dist,-pkg) \fR[\fI\-\-help, \-\-version\fR] .SH "DESCRIPTION" \fBeclean\fP is small tool to remove obsolete portage sources files and binary packages. Used on a regular basis, it prevents your DISTDIR and PKGDIR directories to infinitely grow, while not deleting files which may still be useful. .PP By default, eclean will protect all distfiles or binary packages corresponding to some ebuilds available in the Portage tree. This is the safest mode, since it will protect whatever may still be useful, for instance to downgrade a package without downloading its sources for the second time, or to reinstall a package you unmerge by mistake without recompiling it. Sure, it's also a mode in which your DISTDIR and PKGDIR will stay rather big (although still not growing infinitly). For the 'distfiles', this mode is also quit slow mode because it requiries some access to the whole Portage tree. .PP If you use the \-\-destructive 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 for less usual operations like downgrading or reinstalling an unmerged package. This 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 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. .PP In addition to this main modes, some options allow to declare a few special cases file protection rules: .IP o \-\-time-limit is useful to protect files which are more recent than a given amount of time. .IP o \-\-size-limit (for distfiles only) is useful if you want to protect files bigger than a given size. .IP o \-\-fetch-restricted (for distfiles only) is useful to protect manually downloaded files. But it's also very slow (again, it's a reading of the whole Portage tree data)... .IP o Finally, you can list some categories or package names to protect in exclusion files (see \fBEXCLUSION FILES\fP below). .SH "PARAMETERS" .SS "Global options" .TP \fB\-C, \-\-nocolor\fP turn off colors on output .TP \fB\-d, \-\-destructive\fP only keep the minimum for a reinstallation .TP \fB\-e, \-\-exclude\-file=\fP path to the exclusion file \fB\fP is the absolute path to the exclusion file you want to use. When this option is not used, default paths are /etc/eclean/{packages,distfiles}.exclude (if they exist). Use /dev/null if you have such a file at it standard location and 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) .TP \fB\-p, \-\-pretend\fP only display what would be cleaned .TP \fB\-q, \-\-quiet\fP be as quiet as possible, only display errors .TP \fB\-t, \-\-time-limit=