On Thu, 27 Nov 2014, Michael Tokarev wrote:
(The Built-Using field generation is a bit fun here: I asked on IRC
how people identify which libc is in use, and got various somewhat-
incpmplete replies (the prob is that on different arches, libc package
is named differently). So I invented my
28.11.2014 15:11, Thorsten Glaser wrote:
On Thu, 27 Nov 2014, Michael Tokarev wrote:
(The Built-Using field generation is a bit fun here: I asked on IRC
how people identify which libc is in use, and got various somewhat-
incpmplete replies (the prob is that on different arches, libc package
On Fri, 28 Nov 2014, Michael Tokarev wrote:
‣ intimate knowledge of the build system required, so you know
what precidely is pulled in (reading shlibs:Depends from the
build of the shared version is almost certainly wrong)
Why it is wrong? To be this looks like the most accurate
28.11.2014 18:06, Thorsten Glaser wrote:
On Fri, 28 Nov 2014, Michael Tokarev wrote:
‣ intimate knowledge of the build system required, so you know
what precidely is pulled in (reading shlibs:Depends from the
build of the shared version is almost certainly wrong)
Why it is wrong? To
On Fri, 28 Nov 2014, Michael Tokarev wrote:
Um. Maybe we should assume exact versions of software running in
buildds too?
No, only things that end up in the binaries.
BTW, how about somethig like gcc -v (I'm not sure it is the right
option actually) which shows all libs it actually used
Hello,
Now that perl is out of the base system again, I've had a look at the
figures of a base system install. We're ~80Mib bigger, from 277MiB to
360MiB:
- aptitude is not installed by default any more - -18MiB
- grub got 12MiB bigger.
- wget now depends on libicu52, 27MiB.
- linux-image got
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
[see attachment: DSDT.dsl.xz]
-BEGIN PGP SIGNATURE-
Version: GnuPG v2
iEYEARECAAYFAlR5cWgACgkQ5+rBHyUt5wuLOACgnlJknSuh5qw298OlSQD+tnNZ
KOUAoIm4bc5mqk5bFgMNG73FvURMlov+
=3od8
-END PGP SIGNATURE-
DSDT.dsl.xz
Description:
7 matches
Mail list logo
