1 |
On Mon, 22 Jan 2018 11:28:21 +0100 |
2 |
"Andreas K. Huettel" <dilfridge@g.o> wrote: |
3 |
> Am Montag, 22. Januar 2018, 08:01:08 CET schrieb Zac Medico: |
4 |
> > According to Gentoo policy, future ebuild dependency changes need |
5 |
> > to be accompanied by a revision bump in order to trigger rebuilds |
6 |
> > for users. Therefore, you should only need to use --changed-deps=y |
7 |
> > for a single deep @world update. After that, if you encounter |
8 |
> > installed packages with outdated dependencies in a future deep |
9 |
> > @world update, then you should report it as a bug. |
10 |
> |
11 |
> Did you come up with a solution how to handle eclass-generated |
12 |
> dependency changes then? |
13 |
> |
14 |
> I'd loathe to have to do identical revision bumps for, say, all perl- |
15 |
> module.eclass consumers... |
16 |
|
17 |
perl-cleaner is rather strong evidence that the Perl situation needs a |
18 |
major change anyway... |
19 |
|
20 |
-- |
21 |
Ciaran McCreesh |