[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Packaging of static libraries



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Sun, Apr 10, 2016 at 09:06:50PM +0500, Andrey Rahmatullin wrote:
> On Sun, Apr 10, 2016 at 05:57:16PM +0200, Andreas Tille wrote:
> > > > whether it is advisable to try hard to provide static libraries even if
> > > > upstream build system does not easily provide both.
> > > Note that it's only a wishlist severity bug if you don't provide it.
> > I do not mind about the severity of the bug (since IMHO also wishlist
> > bugs should be closed).  My point was that to my understanding people
> > are misunderstanding policy when giving the advise to ignore static
> > library.
> If you want to provide them it's fine, I don't think anybody will stop you
> (and if there are reasons, we should update the policy). You are just not
> obliged to do that work if you don't have enough resources or it's too
> complicated.

I think we all agree here.  Static libraries should be provided if possible,
but it's acceptable if you don't do it.  However, as Andreas points out, if
people are advising in general to not package static libraries (or worse, to
remove them from a package), that is wrong.

In specific cases it can be fine ("it seems to be hard to do it here, I
wouldn't bother"), but not in general ("packages shouldn't contain static
libraries").

Thanks,
Bas
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1

iQIcBAEBAgAGBQJXCnwoAAoJEJzRfVgHwHE6WiIP/21an2YKFamUTAMY9EfAWo+U
L46eEk6zWaMUtUYVwN+lnwiMWxoRLZqBucksh6u2eF62VpZ3XwkyXQLJnVbdEGUS
nCSsJFGm5W/VxD3DsMhdSmEhkI/XajkglC5+RZnOcLt8b+UW/xa5gDmLi9XybS76
N8ep2bx5MLoO8XyaCR3dABKDBqXcgReys9Vr7wps4u+ocXCw34icphQ8mgJxn1kN
XSixGvsV8tDAhnAuzqZLHz+hRMZo0IQ6+UewKr0gYaMgVp5gWRbi70+RP6jj/qkN
UqDE0nLYcaMtvU7xt308Guuln+SEyhy44RXLJUHmf8lwQWG+fg7nXXrGPfMYjRjr
YmeaC329gOzKkggVbu/TdN5tgDLNP10uGMV/4mve0O3HCOzmd9P8qOfdeXIjpjxQ
WXNgQ1qEC9c7qufSDFGAoYSzN8P1DlomxDn6gEhNCl/XQwLuetxdVifkgNcScfxF
PWv1oYUwoEBSb4ULHqToLBOXSr1HTm5ZOeReGwj27zpL9KEtk03wUWSNFRveB1D3
eno90VtbCtWCLi00VxvQDBJKcA4ZlMjXPZA0b9sPgTfgKQ+6jKuYbDIcpUWdjeF4
EgOewNZW3EaAfrbLae4LrX0wwtrBNPte4h1lrpEaJq5Fl3mzmEM3C2qgxOevIrgr
GZTMwySVZlWXHcUVtHfP
=pEit
-----END PGP SIGNATURE-----


Reply to: