| 1 |
On Mon, 22 Jan 2018 11:28:21 +0100 |
| 2 |
"Andreas K. Huettel" <dilfridge@g.o> wrote: |
| 3 |
|
| 4 |
> Am Montag, 22. Januar 2018, 08:01:08 CET schrieb Zac Medico: |
| 5 |
> > |
| 6 |
> > According to Gentoo policy, future ebuild dependency changes need |
| 7 |
> > to be accompanied by a revision bump in order to trigger rebuilds |
| 8 |
> > for users. Therefore, you should only need to use --changed-deps=y |
| 9 |
> > for a single deep @world update. After that, if you encounter |
| 10 |
> > installed packages with outdated dependencies in a future deep |
| 11 |
> > @world update, then you should report it as a bug. |
| 12 |
> |
| 13 |
> Did you come up with a solution how to handle eclass-generated |
| 14 |
> dependency changes then? |
| 15 |
> |
| 16 |
> I'd loathe to have to do identical revision bumps for, say, all perl- |
| 17 |
> module.eclass consumers... |
| 18 |
|
| 19 |
Isn't there a rule about allowing existing dependency version bumps? I |
| 20 |
can't remember exactly how it went. Something about subsets. ;) |
| 21 |
|
| 22 |
-- |
| 23 |
James Le Cuirot (chewi) |
| 24 |
Gentoo Linux Developer |
Archives