| From: | Magnus Hagander <magnus(at)hagander(dot)net> |
|---|---|
| To: | Devrim Gündüz <devrim(at)gunduz(dot)org> |
| Cc: | Dave Page <dpage(at)pgadmin(dot)org>, PostgreSQL WWW <pgsql-www(at)postgresql(dot)org> |
| Subject: | Re: EPEL and PowerTools to instructions |
| Date: | 2020-11-04 14:54:34 |
| Message-ID: | CABUevEynFFo4J80TEkKjajvHGPF0O5nQUj36JAtYuF26WZ3Szg@mail.gmail.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-www |
On Wed, Nov 4, 2020 at 3:20 PM Devrim Gündüz <devrim(at)gunduz(dot)org> wrote:
>
>
> Hi,
>
> On Wed, 2020-11-04 at 14:07 +0100, Magnus Hagander wrote:
> > Is there some (easy) way to determine exactly which packages need
> > which of them, that we could somehow even turn into a list on the sit
> > (could be directly on yum.postgresql.org or on the main website
> > depending on the size)
>
> Only PostGIS needs it IIRC. I'll check as soon as I can.
And that's the same for both EPEL and PowerTools?
If we can stick to that then it obviously makes things easier. But
then we also need something in the process to make sure that we update
that list if you end up adding another package that needs it.
--
Magnus Hagander
Me: https://www.hagander.net/
Work: https://www.redpill-linpro.com/
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Daniel Gustafsson | 2020-11-05 20:06:25 | Broken links on contributor profiles |
| Previous Message | Devrim Gündüz | 2020-11-04 14:20:12 | Re: EPEL and PowerTools to instructions |