From nobody Tue Dec 12 18:35:15 2023 X-Original-To: ports@mlmmj.nyi.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2610:1c1:1:606c::19:1]) by mlmmj.nyi.freebsd.org (Postfix) with ESMTP id 4SqS3H0ZGRz54H6y for ; Tue, 12 Dec 2023 18:35:23 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Received: from echo.brtsvcs.net (echo.brtsvcs.net [IPv6:2607:f740:c::4ae]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id 4SqS3G5m0rz3Sbp for ; Tue, 12 Dec 2023 18:35:22 +0000 (UTC) (envelope-from list_freebsd@bluerosetech.com) Authentication-Results: mx1.freebsd.org; none Received: from chombo.houseloki.net (65-100-43-2.dia.static.qwest.net [65.100.43.2]) by echo.brtsvcs.net (Postfix) with ESMTPS id 7E9C838D86; Tue, 12 Dec 2023 18:35:14 +0000 (UTC) Received: from [10.26.25.100] (ivy.pas.ds.pilgrimaccounting.com [10.26.25.100]) by chombo.houseloki.net (Postfix) with ESMTPSA id 0150774CD7; Tue, 12 Dec 2023 10:35:13 -0800 (PST) Message-ID: Date: Tue, 12 Dec 2023 10:35:15 -0800 List-Id: Porting software to FreeBSD List-Archive: https://lists.freebsd.org/archives/freebsd-ports List-Help: List-Post: List-Subscribe: List-Unsubscribe: Sender: owner-freebsd-ports@freebsd.org X-BeenThere: freebsd-ports@freebsd.org MIME-Version: 1.0 User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:102.0) Gecko/20100101 Thunderbird/102.15.1 Subject: Re: Another morning lost to bad ports choices (perl upgrade, plus postgres) To: Piotr Smyrak , ports@freebsd.org References: <034BDF27-C9FC-4EBC-901E-21A4BB81AF31@gushi.org> <20231212151637.74a0a94b@daleth.home> Content-Language: en-US From: list_freebsd@bluerosetech.com In-Reply-To: <20231212151637.74a0a94b@daleth.home> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Rspamd-Pre-Result: action=no action; module=replies; Message is reply to one we originated X-Spamd-Result: default: False [-4.00 / 15.00]; REPLY(-4.00)[]; ASN(0.00)[asn:36236, ipnet:2607:f740:c::/48, country:US] X-Spamd-Bar: ---- X-Rspamd-Queue-Id: 4SqS3G5m0rz3Sbp On 2023-12-12 6:16, Piotr Smyrak wrote: > 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 The correct incantation would be "DEFAULT_VERSIONS+= pgsql=foo". You'd also have to set it for everything that uses pgsql and rebuild all of those ports. That introduces the risk of dependency mismatches unless you use a build-in-quarantine system like poudriere and install only from a private repo. The cheap workaround is running postgresql-server in a jail so it doesn't have to chase PGSQL_DEFAULT with the rest of the system.