1 |
On Tue, Jun 05, 2012 at 07:18:01PM -0700, Zac Medico wrote: |
2 |
> On 06/05/2012 05:51 PM, Michael Weber wrote: |
3 |
> > Is there any chance to detect this ZLIB_VERSION problem with |
4 |
> > revdep-rebuild (worst case: add a list of possibly broken packages |
5 |
> > with tests)? |
6 |
> |
7 |
> I'd suggest a special ebuild phase to check for ABI changes, like the |
8 |
> pre_pkg_preinst_abi_check phase suggested here: |
9 |
> |
10 |
> https://bugs.gentoo.org/show_bug.cgi?id=192319#c20 |
11 |
|
12 |
Same thing I said in '07; I don't have a problem w/ hooks for ebuilds |
13 |
to specify additional QA checks, but this *cannot* be the user's end |
14 |
solution- it needs to be purely for making it easier for devs to spot |
15 |
their screwups. In other words, revdep-rebuild shouldn't be involved; |
16 |
this should spot/complain that zlib (for example) changed abi w/out a |
17 |
matching metadata setting/whatever, rather than having checks done in |
18 |
the consumers. |
19 |
|
20 |
Using this for anything other than a QA check of the originating |
21 |
package, basically has an end result of us going towards a |
22 |
non-deterministic resolution model- which is a clusterfuck, frankly. |
23 |
|
24 |
~harring |