Pixel a écrit :
> Guillaume Rousse <Guillaume.Rousse@(protected):
>
>> Herton Ronaldo Krzesinski a écrit :
>>> Pixel <pixel@(protected):
>>> + Revision: 215279
>>> - add rpm filetrigger running "ldconfig -X" when rpm install/remove libraries
>>> - drop patch5 since ldconfig is now nicely handled using rpm filetrigger
>> Does it means we can now remove ldconfig invocation from library packages ?
>
> well, more precisely, we must remove it, otherwise it will now be done
> twice.
>
> the only ldconfig calls that must be kept are the one for libraries
> (wrongly) using ld.so.conf.d (ie using ldconfig cache to do something
> more than a cache should do)
>
>> Or, probably better, call an rpm macro that would do nothing starting from
>> 2009.0, and invoke ldconfig before ?
>
> hum, i was thinking removing them altogether would be enough.
>
> we would really need to have a list of packages needing to be
> backportable...
Or a list of versions that need to be handled for backportability ? We
always failed to find a consensus there.

> now, how can a macro handle things like:
>
> ----
> %post X11
> %{update_menus}
> %{update_desktop_database}
> ----
>
> maybe we can simply wrap things with:
>
> %if %{mdkversion} < 200900
> ...
> %endif
Absolutly. This does not even imply releasing an updated macro
definition for older version :)

>
>> And the same apply to other situation too, for which we already have rpm
>> macro:
>> - updating menus
>
> this one is done. update-menus calls should go.
Cool.
--
Guillaume Rousse
Moyens Informatiques - INRIA Futurs
Tel: 01 69 35 69 62