| 1 |
-- Per Wigren <wigren@××××.se> spake thusly: |
| 2 |
|
| 3 |
> But how do we check that with the current information? |
| 4 |
> To use the postfix-case above as an example.. |
| 5 |
> Postfix works fine with both MySQL v3.x and MySQL v4.x. |
| 6 |
> If it is compiled against v3 it has to be recompiled if MySQL is |
| 7 |
> upgraded from v3 to v4, but not if it is upgraded from v4.0.11 to |
| 8 |
> v4.0.12.. |
| 9 |
> |
| 10 |
> To use MPlayer as another example.. |
| 11 |
> MPlayer has to be recompiled EVERY TIME that DirectFB is upgraded, |
| 12 |
> even minor version, because it links to .so.<complete versionnumber> |
| 13 |
> .. But it doesn't need to be recompiled if for example Vorbis is |
| 14 |
> upgraded from v1.0.1 to v1.0.2 or even v1.8.5 because it links to |
| 15 |
> libvorbis.so.0 ... |
| 16 |
|
| 17 |
Those may be two different answers. In the case of MySQL, perhaps 4.0 |
| 18 |
should've been a different slot? In the case of MPlayer, clearly |
| 19 |
portage needs a new feature which allows either MPlayer or DirectFB to |
| 20 |
specify that a recompile needs to happen when DirectFB is upgraded. |
| 21 |
|
| 22 |
Perhaps it would make more sense for it to be specified in the |
| 23 |
dependancy, because that would allow MySQL 4.0 to specify the same |
| 24 |
thing. Of course, you'd need to base it on version: |
| 25 |
|
| 26 |
RECOMPILE_DEPENDS="<DirectFB-${PV}" or |
| 27 |
RECOMPILE_DEPENDS="*" |
| 28 |
|
| 29 |
RECOMPILE_DEPENDS="<MySQL-4.0" |
| 30 |
|
| 31 |
|
| 32 |
-- |
| 33 |
gentoo-dev@g.o mailing list |
Archives