projects / portage.git / commit
? search:
summary | shortlog | log | commit | commitdiff | tree
(parent: cd08c94) | patch
When portage updates itself and the new version either inherits
authorZac Medico <zmedico@gentoo.org>
Tue, 31 Aug 2010 18:45:28 +0000 (11:45 -0700)
committerZac Medico <zmedico@gentoo.org>
Tue, 31 Aug 2010 18:45:28 +0000 (11:45 -0700)
commit75dab994c4a3e7c38ea29cc633706c435991da05
treeed60a2e5ef4ffa3f93f4cb82104b1ee93923bf95tree | snapshot
parentcd08c946dce4f9f5466597e92ce9df3b0ff197bdcommit | diff
When portage updates itself and the new version either inherits
git.eclass or has 9999 in its version, trigger the 'use copy of current
sources for install, then restart portage' routine. This is required
since with the live git portage-9999 ebuild we can't use the version
to detect incompatible changes to ebuild.sh. This issue was noticed
due to recent versions of ebuild.sh expecting PORTAGE_BZIP2_COMMAND to
be set, causing incompatibility with installed portage-9999 instances.
pym/_emerge/Scheduler.py diff | blob | history
pym/_emerge/depgraph.py diff | blob | history
pym/portage/dbapi/vartree.py diff | blob | history
Unnamed repository; edit this file 'description' to name the repository.