Summary: | portage does not detect cache invalidity triggered by special environment variables | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Michał Górny <mgorny> |
Component: | Core - Ebuild Support | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | minor | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Michał Górny
2012-12-13 18:54:41 UTC
(In reply to comment #0) > [1]:http://article.gmane.org/gmane.linux.gentoo.python/289 I would suggest to copy the eclass to an overlay and modify it there if you need to. Or if you don't want to do that, then just apply your changes to the eclass in the main tree, and mask the experimental flags if necessary. Note that masked flags do not trigger emerge --newuse or --changed-use, so it won't hurt users in that respect. (In reply to comment #1) > (In reply to comment #0) > > [1]:http://article.gmane.org/gmane.linux.gentoo.python/289 > > I would suggest to copy the eclass to an overlay and modify it there if you > need to. Or if you don't want to do that, then just apply your changes to > the eclass in the main tree, and mask the experimental flags if necessary. > Note that masked flags do not trigger emerge --newuse or --changed-use, so > it won't hurt users in that respect. It's not about experimental or special flags. It's just switching the supported Python implementations without a need to modify the ebuilds by hand. |