| 1 |
Am 01.02.2014 20:38, schrieb Arfrever Frehtes Taifersar Arahesis: |
| 2 |
> Handling of inheritance of updates settings |
| 3 |
> (${repository_location}/profiles/updates/*) is broken in Portage |
| 4 |
> and triggers DeprecationWarnings. |
| 5 |
> |
| 6 |
> Current behavior: - When profiles/updates directory exists in |
| 7 |
> repository X, then only settings from this directory are used for |
| 8 |
> packages installed from repository X. - When profiles/updates |
| 9 |
> directory does not exist in repository X, then only settings from |
| 10 |
> profiles/updates directory of repository set in (scheduled for |
| 11 |
> deprecation) 'main-repo' attribute of 'DEFAULT' section in |
| 12 |
> repos.conf are used for packages installed from repository X, |
| 13 |
> regardless of value of 'masters' attribute in metadata/layout.conf |
| 14 |
> of repository X. |
| 15 |
> |
| 16 |
> Suggested behavior: - Support for new 'updates-masters' attribute |
| 17 |
> in metadata/layout.conf. If this attribute is not set explicitly, |
| 18 |
> then it defaults to value of 'masters' attribute. - Settings from |
| 19 |
> profiles/updates directories in repository X and repositories set |
| 20 |
> in 'updates-masters' attribute in metadata/layout.conf of |
| 21 |
> repository X are used for packages installed from repository X. |
| 22 |
> |
| 23 |
> (If a repository containing profiles/updates directory wants to |
| 24 |
> still not inherit updates settings from master repositories, then |
| 25 |
> it will need 'updates-masters =' in metadata/layout.conf.) |
| 26 |
> |
| 27 |
|
| 28 |
+1 |
| 29 |
|
| 30 |
The old behavior doesn't make any sense and the new one is in line |
| 31 |
what's done for every other thing inherited from the masters. |
| 32 |
|
| 33 |
> -- Arfrever Frehtes Taifersar Arahesis |
| 34 |
> |
Archives