Update --depclean and package.provided docs to indicate interaction

between them.

svn path=/main/trunk/; revision=10563

2 files changed, 20 insertions, 9 deletions

diff --git a/man/emerge.1 b/man/emerge.1
index 5bb48952..b01e8374 100644
--- a/man/emerge.1
+++ b/man/emerge.1
@@ -97,17 +97,23 @@ setups that the user may wish to run.
 .BR \-\-depclean
 Cleans the system by removing packages that are not associated
 with explicitly merged packages. Depclean works by creating the
-full dependency tree from the system list and the world file,
+full dependency tree from the system and world sets,
 then comparing it to installed packages. Packages installed, but
-not associated with an explicit merge are listed as candidates
-for unmerging. Inexperienced users are advised to use \fB\-\-pretend\fR
+not part of the dependency tree, will be uninstalled by depclean.
+Inexperienced users are advised to use \fB\-\-pretend\fR
 with this option in order to see a preview of which packages
-will be uninstalled. \fBWARNING: Removing some
+will be uninstalled.
+
+\fBWARNING: Removing some
 packages may cause packages which link to the removed package 
 to stop working and complain about missing libraries.\fR
 Rebuild the complaining package to fix this issue.  Also see
 \fB\-\-with\-bdeps\fR for behavior with respect to build time dependencies that
-are not strictly required. Depclean serves as a dependency aware
+are not strictly required. Note that packages listed in
+package.provided (see \fBportage\fR(5)) may be removed by
+depclean, even if they are part of the world set.
+
+Depclean serves as a dependency aware
 version of \fB\-\-unmerge\fR. When given one or more atoms, it will
 unmerge matched packages that have no reverse dependencies. Use
 \fB\-\-depclean\fR together with \fB\-\-verbose\fR to show reverse
diff --git a/man/portage.5 b/man/portage.5
index 9164ada8..d6eb83cb 100644
--- a/man/portage.5
+++ b/man/portage.5
@@ -213,15 +213,20 @@ useful for stage builders.
 .TP
 .BR package.provided
 A list of packages (one per line) that portage should assume have been 
-provided.  Useful for porting to non-Linux systems.  Portage will not 
-attempt to update a package that is listed here unless another package 
-explicitly requires a version that is newer than what has been listed.  
-Basically, it's a list that replaces the \fBemerge \-\-inject\fR syntax.
+provided.  Useful for porting to non-Linux systems. Basically, it's a
+list that replaces the \fBemerge \-\-inject\fR syntax.
 
 For example, if you manage your own copy of a 2.6 kernel, then you can 
 tell portage that 'sys-kernel/development-sources-2.6.7' is already taken 
 care of and it should get off your back about it.
 
+Portage will not attempt to update a package that is listed here unless
+another package explicitly requires a version that is newer than what
+has been listed. Dependencies that are satisfied by package.provided
+entries may cause installed packages satisfying equivalent dependencies
+to be removed by \fBemerge\fR(1) \fB\-\-depclean\fR actions (see the
+\fBACTIONS\fR section of the \fBemerge\fR(1) man page for more information).
+
 Virtual packages (virtual/*) should not be specified in package.provided.
 Depending on the type of virtual, it may be necessary to add an entry to the
 virtuals file and/or add a package that satisfies a virtual to