Summary: | portage should track the version of gcc used to build a package | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Duncan <1i5t5.duncan> |
Component: | Enhancement/Feature Requests | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED LATER | ||
Severity: | enhancement | CC: | dberkholz, thestick613 |
Priority: | High | ||
Version: | 2.1 | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Duncan
2006-07-31 02:57:35 UTC
Well, I don't think a feature like this should be gcc specific. There are lots of different languages/compilers used for various types of ebuilds. I think it should be the ebuild's job to tell portage what kind of compiler it used. Adding arbitrary keys to the VDB is not currently feasable, and that is essentially what you are asking for. *** Bug 187268 has been marked as a duplicate of this bug. *** |