Date: Tue, 12 Dec 2023 15:16:37 +0100 From: Piotr Smyrak <ps.ports@smyrak.com> To: ports@freebsd.org Subject: Re: Another morning lost to bad ports choices (perl upgrade, plus postgres) Message-ID: <20231212151637.74a0a94b@daleth.home> In-Reply-To: <ab5ed4b4-1706-a425-fb77-c226c62ffda0@bluerosetech.com> References: <034BDF27-C9FC-4EBC-901E-21A4BB81AF31@gushi.org> <ab5ed4b4-1706-a425-fb77-c226c62ffda0@bluerosetech.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, 12 Dec 2023 04:01:23 -0800
list_freebsd@bluerosetech.com wrote:
> On 2023-10-24 15:12, Dan Mahoney (Ports) wrote:
> > Yes, I know that I should be ready to upgrade to 15 at some point,
> > on whatever quarterly port boundary it's decided, "I guess that's
> > when", with no advance notice, via the full stupid dump-and-restore
> > process.
>
> I know it's too late now, but run postgresql-server in its own jail.
> Among other administrative advantages, it splits the
> postgresql-client dependency tree so you don't have to upgrade your
> database server every time the Ports Tree bumps PGSQL_DEFAULT.
> PostgreSQL clients tend to have excellent backward compatibility, so
> as a rule the server just needs to be a supported version.
>
Or you can diverge the PGSQL_DEFAULT between server and client:
.if ${.CURDIR:M*/databases/postgresql${YOUR_FAV_SERVER_VERSION}-server}
PGSQL_DEFAULT=foo
.endif
--
Piotr Smyrak
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20231212151637.74a0a94b>