Summary: | savedconfig.eclass: save path issues when using custom PORTAGE_CONFIGROOT | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | DaboD <daiderek> |
Component: | Eclasses | Assignee: | Gentoo's Team for Core System packages <base-system> |
Status: | UNCONFIRMED --- | ||
Severity: | normal | ||
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Attachments: |
This patch let savedconfig check only directories relative to ${ROOT}
savedconfig.patch |
Description
DaboD
2011-05-15 07:33:07 UTC
Created attachment 273241 [details, diff]
This patch let savedconfig check only directories relative to ${ROOT}
Comment on attachment 273241 [details, diff]
This patch let savedconfig check only directories relative to ${ROOT}
ROOT isnt valid in src_*
Created attachment 336730 [details, diff]
savedconfig.patch
IMHO the config files should be saved and retrieved from a directory relative to PORTAGE_CONFIGROOT. The reason for that is because they're kept inside /etc/portage, which is relative to the PORTAGE_CONFIGROOT path.
Please find attached a patch that implements this.
Comment on attachment 336730 [details, diff] savedconfig.patch (In reply to comment #3) sorry, but this isn't really working for me either. packages should not be writing outside of $D. i think the right thing might be to ignore PORTAGE_CONFIGROOT when saving. it sucks, but there isn't a good alternative. |