[arch-general] Fwd: [signoff] [extra] postfix 3.5.9-1 (WHY?)
Archdevs,
Why are we splitting postfix by backend? Currently the package is only 1.5M
total. Why would we want to fragment postfix backend capability into separate
packages? With 1T+ average drive size the additional fragmentation doesn't
make any space savings sense.
-------- Forwarded Message --------
Subject: [arch-dev-public] [signoff] [extra] postfix 3.5.9-1
Date: Fri, 22 Jan 2021 21:27:43 +0100
From: David Runge via arch-dev-public
Hey, On Sun, 24 Jan 2021 at 00:02, David C. Rankin via arch-general < arch-general@lists.archlinux.org> wrote:
Archdevs,
Why are we splitting postfix by backend? Currently the package is only 1.5M total. Why would we want to fragment postfix backend capability into separate packages? With 1T+ average drive size the additional fragmentation doesn't make any space savings sense.
If you want to do a fair estimation of space saving, you also have to take into account the size of the dependencies for each back-end. To get an idea, I ran `pacman -S postfix` in a clean chroot, and the result is 41.36 MB of extra disk usage (ignoring the package cache), 36.26 MB of which is for different backends (pcre and sqlite were already pulled in by the base package). Whether that space matters or not depends on a lot of things, but I think its nice that you can avoid pulling in unnecessary dependencies. So thank you David! Kind regards, Maarten ``` sudo pacman -r root -S postfix resolving dependencies... looking for conflicting packages... Package (8) New Version Net Change Download Size core/db 5.3.28-5 6.41 MiB core/libaio 0.3.112-2 0.02 MiB core/libnsl 1.3.0-1 0.19 MiB core/lzo 2.10-3 0.39 MiB extra/mariadb-libs 10.5.8-1 22.99 MiB extra/postgresql-libs 13.1-3 6.80 MiB extra/tinycdb 0.78-5 0.06 MiB 0.03 MiB extra/postfix 3.5.8-4 4.50 MiB 1.39 MiB Total Download Size: 1.42 MiB Total Installed Size: 41.36 MiB ```
On Sat, 23 Jan 2021 at 23:46, Maarten de Vries via arch-general
Hey,
On Sun, 24 Jan 2021 at 00:02, David C. Rankin via arch-general < arch-general@lists.archlinux.org> wrote:
Archdevs,
Why are we splitting postfix by backend? Currently the package is only 1.5M total. Why would we want to fragment postfix backend capability into separate packages? With 1T+ average drive size the additional fragmentation doesn't make any space savings sense.
If you want to do a fair estimation of space saving, you also have to take into account the size of the dependencies for each back-end.
To get an idea, I ran `pacman -S postfix` in a clean chroot, and the result is 41.36 MB of extra disk usage (ignoring the package cache), 36.26 MB of which is for different backends (pcre and sqlite were already pulled in by the base package). Whether that space matters or not depends on a lot of things, but I think its nice that you can avoid pulling in unnecessary dependencies.
Allow me to put forward an alternative idea: It should be fairly easy, to have the best of both worlds by demoting the separate backend dependencies to optdepends. This way there is no splitting of a trivial package and anyone wishing to utilise backend Foo, should already have it installed and configured. HTH -Emil
On 1/23/21 5:43 PM, Maarten de Vries wrote:
To get an idea, I ran `pacman -S postfix` in a clean chroot, and the result is 41.36 MB of extra disk usage (ignoring the package cache), 36.26 MB of which is for different backends (pcre and sqlite were already pulled in by the base package). Whether that space matters or not depends on a lot of things, but I think its nice that you can avoid pulling in unnecessary dependencies.
So thank you David!
Kind regards, Maarten
Okay, That makes more sense. I was not thinking dependencies. Thank you. -- David C. Rankin, J.D.,P.E.
participants (3)
-
David C. Rankin
-
Emil Velikov
-
Maarten de Vries