Summary: | Let emerge store resolve information in a file, and resolve using past resolutions | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Alexander Berntsen (RETIRED) <bernalex> |
Component: | Core - Interface (emerge) | Assignee: | Portage team <dev-portage> |
Status: | CONFIRMED --- | ||
Severity: | normal | CC: | esigra, kingjon3377, pacho |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | 528394 | ||
Bug Blocks: | 155723 |
Description
Alexander Berntsen (RETIRED)
2016-10-06 11:01:17 UTC
(In reply to Alexander Berntsen from comment #0) > DETAILS > ======= > There needs to be a way to validate whether the resolution is outdated (and > therefore useless). Zac suggests to store state hashes for all package > repositories, the installed package database, and the portage configuration. > He also thinks we should assert that users can't modify ebuilds without > updating the state hash. This all sounds reasonable to me. This part ties in with bug 528394. |