Summary: | enable portage to get and write down the max size of used memory when emerging some package | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Rumen Yotov <rumen> |
Component: | Conceptual/Abstract Ideas | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED WONTFIX | ||
Severity: | enhancement | ||
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Rumen Yotov
2004-12-08 13:14:55 UTC
CFLAGS and USE could have a huge impact on that value Hi, Of course it greatly depends, but this info will be user-config-specific (if i don't change my CFLAGS,USE-flags too much). Will use previous version's value. In a slowly changing config the value will be near the truth. Have also see some problem with new packages which are much bigger than previous so that mem-size value may be uncorrect. May be use one more ;-) global USE-flag: 'use-tmpfs' and load it in fstab on boot. Rumen This won't be done by us. The next major release of portage will support a plugin system to some degree that should be capable of supporting this externally. |