1 |
I'm annoyed about impossibility to fix a certain class of breakages |
2 |
(other than reemerging the failing package). I am referring to the |
3 |
breakages occurred when foo has been upgraded, but the bar package |
4 |
cannot work with it because it was build against the old foo version. |
5 |
|
6 |
We all had to run revdep-rebuild once in awhile, for fixing dynamic |
7 |
linkage problems, but unfortunately revdep-rebuild cannot fix another |
8 |
kind of incompatibility, namely dynamic version check implemented in |
9 |
some packages. |
10 |
For instance, the recent openssl-0.9.8* update broke dev-libs/neon (and |
11 |
consequently subversion) because neon library isn't happy just by |
12 |
linking with libssl.so.0.9.7 but also check the libssl version when |
13 |
loads the ssl library. Another example is the subtle dependency between |
14 |
the pppd version and pppd plugins (net-dialup/pptpd needs to be rebuild |
15 |
every time you change PV of the net-dialup/ppp because pptpd builds a |
16 |
plugin for the ppp daemon). |
17 |
|
18 |
I reckon this could be solved by yet another *DEPEND variable. The only |
19 |
atoms accepted by this variable would be "CATEGORY/PN". Every time when |
20 |
a package gets updated from PV1 to PV2 (distinct versions, revisions |
21 |
will not count), portage will automatically re-emerge those packages |
22 |
that depend on it. |
23 |
|
24 |
Thoughts? |