Summary: | emerge --autounmask-write: It is not defined where the configuration changes are written. | ||
---|---|---|---|
Product: | Portage Development | Reporter: | Johannes Rauh <jarauh> |
Component: | Core | Assignee: | Portage team <dev-portage> |
Status: | RESOLVED FIXED | ||
Severity: | minor | CC: | tomka |
Priority: | Normal | Keywords: | InVCS |
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- | |
Bug Depends on: | |||
Bug Blocks: | 376695, 381649 |
Description
Johannes Rauh
2011-06-08 16:18:01 UTC
If the file is a directory, then it traverses in lexical order and chooses the last file found. So, you could create a file called something like zzz-autounmask if you the changes to go there. I've just realized that the current code writes package.keywords, which could be annoying for people that are using the new package.accept_keywords name. We should fix it to use package.accept_keywords if it exists. (In reply to comment #1) > I've just realized that the current code writes package.keywords, which could > be annoying for people that are using the new package.accept_keywords name. We > should fix it to use package.accept_keywords if it exists. This issue is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=c36d3ea4dec51781f0a1a3f45c3d2565e9ca2f95 So the behaviour of choosing the last file in /etc/portage/package.keywords is a feature, not a bug? If this is the case, then please document in the man pages. Thanks. (In reply to comment #3) > So the behaviour of choosing the last file in /etc/portage/package.keywords is > a feature, not a bug? Right. For example, if one of the files has "foo/bar -*", then any new settings that override it have to be appended to the same file or a later one. The simplest thing to do is to append all changes to the last file. > If this is the case, then please document in the man pages. > Thanks. Ok, will do. This is fixed in git: http://git.overlays.gentoo.org/gitweb/?p=proj/portage.git;a=commit;h=424f8f8d6587f015e074e3e915746929a990a52f This is fixed in 2.1.10.19 and 2.2.0_alpha59. |