Summary: | [Future EAPI] Move default phase functions into the repo | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Michał Górny <mgorny> |
Component: | Eclasses | Assignee: | PMS/EAPI <pms> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | CC: | esigra |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 174380 |
Description
Michał Górny
2011-01-08 10:42:38 UTC
So when you change src_test, you break every single package using the newer EAPI? Doesn't this idea defeat the entire point of having EAPIs? (In reply to comment #1) > So when you change src_test, you break every single package using the newer > EAPI? Doesn't this idea defeat the entire point of having EAPIs? I meant having these implementations EAPI-specific, like eclasses currently do. Then why not just have them as part of the package managers? The code reuse argument doesn't fly, since it's useful to be able to make use of package manager internal things to implement functions and helpers. And if you're sticking to EAPIs, you don't gain anything by making the changes in the tree as opposed to in the EAPI definition. I withdraw this since people don't like it. |