Summary: | Feature Request: /etc/portage: stubs for package.* | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Aaron Tokhy <atokhy> |
Component: | Core - Configuration | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | enhancement | CC: | bernd.glueckert |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Aaron Tokhy
2008-12-14 03:17:27 UTC
I'm not sure if stubs would be worth the extra clutter. As it is, the /etc/portage/package.* can be viewed with `man portage` and there's a reference to that in the "masked packages" section of `man emerge`. If adding templates, I'd suggest to use /etc/portage/package.$foo/99_example instead of single files. I'd be happy with the portage ebuild just creating /etc/portage and dropping a .keep* in there. I'm always annoyed that I have to create the dir for new installs. The idea to make these stubs sounds good because this is an integral part of portage. By the way: Installing stage3 with amd64 architecture (2 weeks ago) will create this sub dirs, installing x86 architecture dont. |