With new-style virtuals, there is no reason to enforce special rules to
virtuals in package.provided. If user wishes to implicitly provide
the virual package, we should not forbid him. Of course, he knows
the implications.
---
man/portage.5 | 7 -------
pym/portage/package/ebuild/config.py | 6 ------
2 files changed, 13 deletions(-)
diff --git a/man/portage.5 b/man/portage.5
index 150294b..46835b5 100644
--- a/man/portage.5
+++ b/man/portage.5
@@ -400,13 +400,6 @@ 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,
-since virtual packages themselves do not provide any files, and
-package.provided is intended to represent packages that do provide files.
-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
-package.provided.
-
.I Format:
.nf
\- comments begin with # (no inline comments)
diff --git a/pym/portage/package/ebuild/config.py
b/pym/portage/package/ebuild/config.py
index 59e239b..4d1f1d5 100644
--- a/pym/portage/package/ebuild/config.py
+++ b/pym/portage/package/ebuild/config.py
@@ -803,12 +803,6 @@ class config(object):
has_invalid_data = True
del pkgprovidedlines[x]
continue
- if cpvr[0] == "virtual":
- writemsg(_("Virtual package in
package.provided: %s\n") % \
- myline, noiselevel=-1)
- has_invalid_data = True
- del pkgprovidedlines[x]
- continue
if has_invalid_data:
writemsg(_("See portage(5) for correct
package.provided usage.\n"),
noiselevel=-1)
--
2.2.0
