summaryrefslogtreecommitdiffstats
path: root/pym/portage_exception.py
diff options
context:
space:
mode:
authorZac Medico <zmedico@gentoo.org>2007-10-05 02:50:59 +0000
committerZac Medico <zmedico@gentoo.org>2007-10-05 02:50:59 +0000
commit7ad0aa456700abec1a8f0ccbefe9ab14189c25ab (patch)
treeae655d7f54adc71e4dd5ea682d636b3415f0b0f9 /pym/portage_exception.py
parentc88960470151c8737595b838acefdedc8be2ac2a (diff)
downloadportage-7ad0aa456700abec1a8f0ccbefe9ab14189c25ab.tar.gz
portage-7ad0aa456700abec1a8f0ccbefe9ab14189c25ab.tar.bz2
portage-7ad0aa456700abec1a8f0ccbefe9ab14189c25ab.zip
When the metadata cache contains a negative EAPI, it means
that the cache entry was generated by a version of portage that did not support the eapi. When the user upgrades to a version that now supports the previously unsupported EAPI, those cache entries need to be regenerated. Therefore, when a cache entry has a negative EAPI, check if the EAPI would be supported and trigger a regen if appropriate. (trunk r7910 and r7919) svn path=/main/branches/2.1.2/; revision=7933
Diffstat (limited to 'pym/portage_exception.py')
0 files changed, 0 insertions, 0 deletions