| From: | Jeremy Schneider <schneider(at)ardentperf(dot)com> |
|---|---|
| To: | Christoph Berg <cb(at)df7cb(dot)de> |
| Cc: | "pgsql-pkg-debian(at)lists(dot)postgresql(dot)org" <pgsql-pkg-debian(at)lists(dot)postgresql(dot)org> |
| Subject: | Re: postgresql-client-common pulling in libipc-run-perl |
| Date: | 2025-01-11 21:14:29 |
| Message-ID: | 20250111131429.79238f82@ardentperf.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-pkg-debian |
On Sat, 11 Jan 2025 22:08:02 +0100
Christoph Berg <cb(at)df7cb(dot)de> wrote:
> Re: Jeremy Schneider
> > So the real question is why the client-common package has a hard
> > requirement on libipc-run-perl, and whether we can make this
> > dependency optional (or remove it). That would trim about 45MB off
> > the base container size, which is meaningful since these base
> > images are very widely used.
>
> You are missing the fact that postgresql-common is written in perl.
lol, yes i sent this email before tracking down what the package is and
what is does and how its written (it looks like a different package from
the postgresql client itself, but its a hard dependency of the client)
i'll go find the code and start reading
-Jeremy
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Jeremy Schneider | 2025-01-11 23:05:06 | Re: postgresql-client-common pulling in libipc-run-perl |
| Previous Message | Christoph Berg | 2025-01-11 21:08:02 | Re: postgresql-client-common pulling in libipc-run-perl |