From 3dc590d344e9155298d92095bafa173e3c40c5c2 Mon Sep 17 00:00:00 2001 From: Zac Medico Date: Wed, 4 Jun 2008 02:01:00 +0000 Subject: Update --depclean and package.provided docs to indicate interaction between them. (trunk r10563) svn path=/main/branches/2.1.2/; revision=10573 --- man/portage.5 | 13 +++++++++---- 1 file changed, 9 insertions(+), 4 deletions(-) (limited to 'man/portage.5') diff --git a/man/portage.5 b/man/portage.5 index aabff9f88..4bee02fad 100644 --- a/man/portage.5 +++ b/man/portage.5 @@ -216,15 +216,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 -- cgit v1.2.3-1-g7c22