The upstream docs state clearly: Virtualenv’s release schedule is tied to pip’s – each time there’s a new pip release, there will be a new virtualenv release that *bundles* the new version of pip. The ebuild isn't removing anything. So...what is the point of having it as an explicit dep ? Is the system copy used at all ?
Thanks for pointing this out.
commit 09080dda2d93b4510488a93d697e5e224d53c52d Author: Justin Lecher <jlec@gentoo.org> Date: Tue Nov 17 11:12:50 2015 +0100 dev-python/virtualenv: Remove unnecessary dependency on pip & setuptools Bundled dev-python/{pip,setuptools,argparse,wheel} cannot be removed, as we have a chicken and egg problem here. In the new virtualenv we need those packages to install them. Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=566022 Package-Manager: portage-2.2.23 Signed-off-by: Justin Lecher <jlec@gentoo.org> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=09080dda2d93b4510488a93d697e5e224d53c52d
commit 49c59b1fde1c081e5c0ac9620fc2fd3fefcfb6e6 Author: Justin Lecher <jlec@gentoo.org> Date: Tue Nov 17 11:12:50 2015 +0100 dev-python/virtualenv: Remove unnecessary dependency on pip & setuptools Bundled dev-python/{pip,setuptools,argparse,wheel} cannot be removed, as we have a chicken and egg problem here. In the new virtualenv we need those packages to install them. Gentoo-Bug: https://bugs.gentoo.org/show_bug.cgi?id=566022 Package-Manager: portage-2.2.23 Signed-off-by: Justin Lecher <jlec@gentoo.org> https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=49c59b1fde1c081e5c0ac9620fc2fd3fefcfb6e6
