> Le 2 oct. 2016 à 14:25, Niels Thykier a écrit :
> As for using a path trigger, I believe that was ruled out as they are
> recursive. The libc-bin package would have to declare an interest in
> *all* of /usr/lib, which will generate tons of false-positives. I
> suspect it may also be a bit hea
Loïc Minier:
> Hi,
>
> [...]
> Another perhaps smarter approach would be to do away with postinst
> requirements entirely by installing
> a ldconfig file-based trigger in libc for *.so files under interesting
directories. This would let
> libc define when to run libc’s ldconfig rather than having
2 matches
Mail list logo
