Summary: | gentoolkit metapackage vs. gentoolkit | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Torsten Veller (RETIRED) <tove> |
Component: | Tools | Assignee: | Portage Tools Team <tools-portage> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Torsten Veller (RETIRED)
2011-12-05 05:35:23 UTC
No, I don't think so at this time. Although, changing gentoolkit into a meta package is a possibility. In that respect, this bug would be a duplicate of bug 391701. I was not aware flaggie was to be added to gentoolkit until reading the bug you listed just now. I have had a couple of requests to have gentoolkit pull in external app-portage utilities. At this point, we are solely in a proof of concept stage so the only ebuild changes are occurring in the gentoolkit-9999 ebuild which is not keyworded for any architectures so we don't impact normal users. However, any external utilities that get added to a meta-ebuild will need to have the same keywords as the core utility in order for it to be useful. That's the reason for the keyword requests. My only real requirement for this work is that if a user does 'emerge gentoolkit', they get the core gentoolkit code at a minimum. Since we are in the proof of concept stage of this, I am open to any suggestions, comments, or concerns and you are free to ping me in IRC, send an email, etc. *** This bug has been marked as a duplicate of bug 391701 *** |