| 1 |
W dniu pon, 22.01.2018 o godzinie 11∶28 +0100, użytkownik Andreas K. |
| 2 |
Huettel napisał: |
| 3 |
> Am Montag, 22. Januar 2018, 08:01:08 CET schrieb Zac Medico: |
| 4 |
> > |
| 5 |
> > According to Gentoo policy, future ebuild dependency changes need to be |
| 6 |
> > accompanied by a revision bump in order to trigger rebuilds for users. |
| 7 |
> > Therefore, you should only need to use --changed-deps=y for a single |
| 8 |
> > deep @world update. After that, if you encounter installed packages with |
| 9 |
> > outdated dependencies in a future deep @world update, then you should |
| 10 |
> > report it as a bug. |
| 11 |
> |
| 12 |
> Did you come up with a solution how to handle eclass-generated dependency |
| 13 |
> changes then? |
| 14 |
> |
| 15 |
> I'd loathe to have to do identical revision bumps for, say, all perl- |
| 16 |
> module.eclass consumers... |
| 17 |
> |
| 18 |
|
| 19 |
I think one of the reasons for the policy back then was to actually stop |
| 20 |
people from creating horribly broken monstrosities of eclasses. |
| 21 |
|
| 22 |
-- |
| 23 |
Best regards, |
| 24 |
Michał Górny |
Archives