/etc/portage/* content parsing doesn't force sorting for ordering of file loading. #385
Assignees
Labels
Comments
ferringb
changed the title
|
As to the fix for this; it should just be a matter of using |
ferringb
added a commit
to ferringb/pkgcore
that referenced
this issue
Dec 26, 2022
Specifically, alphanumeric sorting; a '00' should always be parsed before an '01' or 'a'. The ordering must be stable so that globals- in a 00 file- can be overridden per package via other files. If there is no stable ordering forced on how the order of files read, then this isn't supported. Closes pkgcore#385 Signed-off-by: Brian Harring <ferringb@gmail.com>
ferringb
added a commit
to ferringb/pkgcore
that referenced
this issue
Dec 26, 2022
Specifically, alphanumeric sorting; a '00' should always be parsed before an '01' or 'a'. The ordering must be stable so that globals- in a 00 file- can be overridden per package via other files. If there is no stable ordering forced on how the order of files read, then this isn't supported. Closes pkgcore#385 Signed-off-by: Brian Harring <ferringb@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Package.use in particular is affected by this. Currently pkgcore/ebuild/domain's
load_propertyinvokes livefs iter_scan to get the list of files; that returns whatever ordering the underlying FS uses.That in turn can lead to situations where a 00_* package.use files isn't used as the base for files that follow, leading to incorrect USE stacking.
TL;DR: force ordering here. Portage's logic for this appears to just be a straight up sort, and I can't see any fault w/ doing the same.
The text was updated successfully, but these errors were encountered: