Significant install size differences

RubenKelevra commented

2022-05-09 16:34:35 +02:00

Contributor

I noticed that on a couple of packages the install size reported by pacman is significantly different compared to the regular repo ones:

community-x86-64-v3/faust        2.40.0-1      2.40.0-1.1                       66.46 MiB
extra-x86-64-v3/mariadb          10.7.3-1      10.7.3-1.1                       51.03 MiB 
extra-x86-64-v3/mariadb-clients  10.7.3-1      10.7.3-1.1                       19.68 MiB
extra-x86-64-v3/mesa             22.0.3-1      22.0.3-1.1                       19.91 MiB
extra-x86-64-v3/mesa-vdpau       22.0.3-1      22.0.3-1.1                        3.18 MiB
extra-x86-64-v3/mkvtoolnix-cli   67.0.0-2      67.0.0-2.1                        2.13 MiB
community-x86-64-v3/opnplug       1.0.2-4       1.0.2-4.2                       -6.44 MiB 
community-x86-64-v3/podman        4.0.3-2       4.1.0-1.1                       -4.71 MiB
community-x86-64-v3/stochas       1.3.5-1       1.3.5-1.1                       -4.29 MiB

While I yet not encountered an issue with the packages (as far as I'm actually using them) - it might be worth given a look what's going on in them (and maybe exclude them from pushing to the mirror if a build process is creating massively different sizes - if not manually checked).

I noticed that on a couple of packages the install size reported by pacman is significantly different compared to the regular repo ones: ``` community-x86-64-v3/faust 2.40.0-1 2.40.0-1.1 66.46 MiB extra-x86-64-v3/mariadb 10.7.3-1 10.7.3-1.1 51.03 MiB extra-x86-64-v3/mariadb-clients 10.7.3-1 10.7.3-1.1 19.68 MiB extra-x86-64-v3/mesa 22.0.3-1 22.0.3-1.1 19.91 MiB extra-x86-64-v3/mesa-vdpau 22.0.3-1 22.0.3-1.1 3.18 MiB extra-x86-64-v3/mkvtoolnix-cli 67.0.0-2 67.0.0-2.1 2.13 MiB community-x86-64-v3/opnplug 1.0.2-4 1.0.2-4.2 -6.44 MiB community-x86-64-v3/podman 4.0.3-2 4.1.0-1.1 -4.71 MiB community-x86-64-v3/stochas 1.3.5-1 1.3.5-1.1 -4.29 MiB ``` While I yet not encountered an issue with the packages (as far as I'm actually using them) - it might be worth given a look what's going on in them (and maybe exclude them from pushing to the mirror if a build process is creating massively different sizes - if not manually checked).

anonfunc commented

2022-05-11 16:54:00 +02:00

Owner

This is probably a side-effect of -O3 and can be safely ignored.

This is probably a side-effect of `-O3` and can be safely ignored.

anonfunc added the question label 2022-05-11 16:54:17 +02:00

RubenKelevra commented

2022-05-11 20:56:44 +02:00

Author

Contributor

Interesting. I wouldn't expected THAT much of a difference 🤔

Just an idea, could you run an -O2 compile for those packages on the list (fairly easily) on the build machine - just to be sure that there's nothing else going on?

Would take a long long time on my available hardware :'D

Interesting. I wouldn't expected THAT much of a difference 🤔 Just an idea, could you run an -O2 compile for those packages on the list (fairly easily) on the build machine - just to be sure that there's nothing else going on? Would take a long long time on my available hardware :'D

anonfunc commented

2022-06-19 00:11:28 +02:00

Owner

I don't think much more needs to be said here at the moment. If anything comes up, please reopen.

anonfunc closed this issue

2022-06-19 00:11:29 +02:00

Significant install size differences #108