On 01/11/13 01:40, Sébastien Luttringer wrote:
> On 31/10/2013 14:25, Allan McRae wrote:
>> It is fairly common that packages contain static libraries with no
>> shared counterpart. These should not be removed with !staticlibs.
>
> Why not let packagers do their job and add staticlibs.
> Using "!staticlibs" will no more ensure that static libs are cleaned.
> This make usage of this option less simple and clear than before.
>
I have struck many packages where we have to use options=('staticlibs')
and then manually remove a bunch of static libraries because one needs
to be kept.
I see this as making packaging more simple, because I no longer need to
check whether to apply !staticlibs to a package - it will just do the
right thing.
A
