| 1 |
On 01/22/2018 02:28 AM, Andreas K. Huettel wrote: |
| 2 |
> Am Montag, 22. Januar 2018, 08:01:08 CET schrieb Zac Medico: |
| 3 |
>> |
| 4 |
>> According to Gentoo policy, future ebuild dependency changes need to be |
| 5 |
>> accompanied by a revision bump in order to trigger rebuilds for users. |
| 6 |
>> Therefore, you should only need to use --changed-deps=y for a single |
| 7 |
>> deep @world update. After that, if you encounter installed packages with |
| 8 |
>> outdated dependencies in a future deep @world update, then you should |
| 9 |
>> report it as a bug. |
| 10 |
> |
| 11 |
> Did you come up with a solution how to handle eclass-generated dependency |
| 12 |
> changes then? |
| 13 |
> |
| 14 |
> I'd loathe to have to do identical revision bumps for, say, all perl- |
| 15 |
> module.eclass consumers... |
| 16 |
|
| 17 |
Would it be possible to isolate the dependency changes in virtual |
| 18 |
ebuilds? If the eclass depends on a virtual, the maybe updating to the |
| 19 |
latest version of the virtual can serve as the means apply the needed |
| 20 |
dependency change? |
| 21 |
-- |
| 22 |
Thanks, |
| 23 |
Zac |
Archives