Mailinglist Archive: opensuse-packaging (220 mails)
| < Previous | Next > |
Re: [opensuse-packaging] glibc-devel-static coming to Factory
- From: Michael Matz <matz@xxxxxxx>
- Date: Fri, 17 Jun 2011 14:54:16 +0200 (CEST)
- Message-id: <Pine.LNX.4.64.1106171449250.17115@wotan.suse.de>
Hi,
On Fri, 17 Jun 2011, Richard Guenther wrote:
In this context the wish for explicitely having a package containing the
static library is to know which packages link against libc statically and
hence which ones to recompile should there be a security update for libc.
I don't fully buy this way of thinking, and for libstdc++ it doesn't make
much sense, as much code will always be statically in the application (all
the template expansions).
Ciao,
Michael.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
On Fri, 17 Jun 2011, Richard Guenther wrote:
There is also libstdc++<version>-devel that contains
/usr/lib64/gcc/x86_64-suse-linux/4.5/libstdc++.a which might get
splitted off a different package
No, then -static-libstdc++ doesn't work anymore. Seriously, who cares
about the size of -devel packages??
In this context the wish for explicitely having a package containing the
static library is to know which packages link against libc statically and
hence which ones to recompile should there be a security update for libc.
I don't fully buy this way of thinking, and for libstdc++ it doesn't make
much sense, as much code will always be statically in the application (all
the template expansions).
Ciao,
Michael.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-packaging+help@xxxxxxxxxxxx
| < Previous | Next > |