| 1 |
Handling of inheritance of updates settings (${repository_location}/profiles/updates/*) is broken |
| 2 |
in Portage and triggers DeprecationWarnings. |
| 3 |
|
| 4 |
Current behavior: |
| 5 |
- When profiles/updates directory exists in repository X, then only settings from this directory are |
| 6 |
used for packages installed from repository X. |
| 7 |
- When profiles/updates directory does not exist in repository X, then only settings from profiles/updates |
| 8 |
directory of repository set in (scheduled for deprecation) 'main-repo' attribute of 'DEFAULT' section |
| 9 |
in repos.conf are used for packages installed from repository X, regardless of value of 'masters' attribute |
| 10 |
in metadata/layout.conf of repository X. |
| 11 |
|
| 12 |
Suggested behavior: |
| 13 |
- Support for new 'updates-masters' attribute in metadata/layout.conf. |
| 14 |
If this attribute is not set explicitly, then it defaults to value of 'masters' attribute. |
| 15 |
- Settings from profiles/updates directories in repository X and repositories set in 'updates-masters' |
| 16 |
attribute in metadata/layout.conf of repository X are used for packages installed from repository X. |
| 17 |
|
| 18 |
(If a repository containing profiles/updates directory wants to still not inherit updates settings from |
| 19 |
master repositories, then it will need 'updates-masters =' in metadata/layout.conf.) |
| 20 |
|
| 21 |
-- |
| 22 |
Arfrever Frehtes Taifersar Arahesis |
Archives