Received: from malur.postgresql.org ([217.196.149.56]) by arkaria.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s3224-008bZE-1k for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 23:09:36 +0000 Received: from localhost ([127.0.0.1] helo=malur.postgresql.org) by malur.postgresql.org with esmtp (Exim 4.94.2) (envelope-from ) id 1s3220-00CuUm-I2 for pgsql-general@arkaria.postgresql.org; Fri, 03 May 2024 23:09:33 +0000 Received: from magus.postgresql.org ([2a02:c0:301:0:ffff::29]) by malur.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s321y-00CuUe-SJ for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 23:09:33 +0000 Received: from wfhigh8-smtp.messagingengine.com ([64.147.123.159]) by magus.postgresql.org with esmtps (TLS1.3) tls TLS_ECDHE_RSA_WITH_AES_256_GCM_SHA384 (Exim 4.94.2) (envelope-from ) id 1s321v-001Pj8-2N for pgsql-general@lists.postgresql.org; Fri, 03 May 2024 23:09:31 +0000 Received: from compute1.internal (compute1.nyi.internal [10.202.2.41]) by mailfhigh.west.internal (Postfix) with ESMTP id BDF7F180012D; Fri, 3 May 2024 19:09:22 -0400 (EDT) Received: from mailfrontend1 ([10.202.2.162]) by compute1.internal (MEProxy); Fri, 03 May 2024 19:09:22 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=aklaver.com; h= cc:content-transfer-encoding:content-type:content-type:date:date :from:from:in-reply-to:in-reply-to:message-id:mime-version :references:reply-to:subject:subject:to:to; s=fm2; t=1714777762; x=1714864162; bh=FppWcVikHtjwlVvq+NYte40TrHOj3216z6f6Blyp0h4=; b= texXiMMXjB+YZ6iwR5S5kfSixt49Tnz4AolHxUyE05JLIusOIuUBlY7LyUAr0/OV aejGcxFPCb2GBdmCHVYK73buvfw46y0KZRVUfKvaU3h4/1e/HikeTBwBlQYV337N Gbvfh2+N7QDVcaZjhKVP9827KaCSwzi+0M2f63W25YP3+ZQ+7TXIu/BIQoX+Mp0Y xwe0upVg+cjTONBv6G7dcC6NwvCCcT30nqRFQg/kqY43IaVA6tSTQvG2UF1mGoo8 k1CWaU33A+5xceq6zsQYRZCSK8c7N3Sgd5t/scEfFWUzJWRNzrGK0F/L/YZPJB31 LVPKxgJ7WZ0ASJTUGeLUXw== DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d= messagingengine.com; h=cc:content-transfer-encoding:content-type :content-type:date:date:feedback-id:feedback-id:from:from :in-reply-to:in-reply-to:message-id:mime-version:references :reply-to:subject:subject:to:to:x-me-proxy:x-me-proxy :x-me-sender:x-me-sender:x-sasl-enc; s=fm3; t=1714777762; x= 1714864162; bh=FppWcVikHtjwlVvq+NYte40TrHOj3216z6f6Blyp0h4=; b=A zTO4peWBV2IkabPyRE4MJ/I0VXTTnRQ1D30XTwt9nOEebiky6psPTyu4UyOMx373 8xkomqWBsOMK0HX47h+UM8ya5v1aE6KRNIRQQDS8lXq9U+KsxakZuotH7fkqycWD BIDpTQzPNyeTLrRee/1mY29MDphdFLvSs7MWESty9rZxkU5V0y1oL3X0EwYGp/1I 7QHMbRXx1ZW89ALY2E8GZx3rxlvStwilT8QTowYZ2omP1GhR3B4XQ2LF/S2Rmelw ZGKEYFuwnUvugXDI484bWhrjnUsrubPW1SYjY0qzbUOMTmPZfULx27edMVzDkd9h zNCBtQEWsZ+4NIHV+pImw== X-ME-Sender: X-ME-Received: X-ME-Proxy-Cause: gggruggvucftvghtrhhoucdtuddrgedvledrvddvuddgudekucetufdoteggodetrfdotf fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdfqfgfvpdfurfetoffkrfgpnffqhgen uceurghilhhouhhtmecufedttdenucenucfjughrpefkffggfgfuvfhfhfgjtgfgsehtke ertddtvdejnecuhfhrohhmpeetughrihgrnhcumfhlrghvvghruceorggurhhirghnrdhk lhgrvhgvrhesrghklhgrvhgvrhdrtghomheqnecuggftrfgrthhtvghrnhepgedtfeeuve eiffdvieelheduieduudfhhfeuieegudejhefggeeuveehudeitdeunecuffhomhgrihhn pegvnhhtvghrphhrihhsvggusgdrtghomhdpfigvsghinhhsthgrlhhlrdguvghvpdhpoh hsthhgrhgvshhqlhdrohhrghenucevlhhushhtvghrufhiiigvpedtnecurfgrrhgrmhep mhgrihhlfhhrohhmpegrughrihgrnhdrkhhlrghvvghrsegrkhhlrghvvghrrdgtohhm X-ME-Proxy: Feedback-ID: i76984098:Fastmail Received: by mail.messagingengine.com (Postfix) with ESMTPA; Fri, 3 May 2024 19:09:21 -0400 (EDT) Message-ID: Date: Fri, 3 May 2024 16:09:21 -0700 MIME-Version: 1.0 User-Agent: Mozilla Thunderbird Subject: Re: How to Build Postgres in a Portable / Relocatable fashion? To: AJ ONeal , "pgsql-general@lists.postgresql.org" References: Content-Language: en-US From: Adrian Klaver In-Reply-To: Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 8bit List-Id: List-Help: List-Subscribe: List-Post: List-Owner: List-Archive: Archived-At: Precedence: bulk On 5/3/24 15:57, AJ ONeal wrote: > Back in the good old days there was official 1st-party support for Linux: Still there. The below is for the EDB installer, which at this point is only for MacOS and Windows as Unixen platforms have there own packaging. This was/is a third party site. > https://www.enterprisedb.com/downloads/postgres-postgresql-downloads > > > Those binaries could be |tar xvf|​'d and used without any fuss or muss, > from any location, on any distro. > > I'm the core maintainer of https://webinstall.dev/ >  and I'm thinking to break our "official builds > only" rule because, well, I haven't been able to find any way to get > up-to-date builds from an official channel - and |apt|​ is always > half-a-decade out-of-date (part of the reason for Webi, but Webi is far > worse in this case, stuck at v10). I don't see that. Using PGDG repo on Ubuntu 22.04: apt list --installed | grep postgres postgresql-14/jammy-pgdg,now 14.11-1.pgdg22.04+1 amd64 [installed] postgresql-15-pgtap/jammy-pgdg,now 1.3.3-1.pgdg22.04+1 all [installed] postgresql-15/jammy-pgdg,now 15.6-1.pgdg22.04+1 amd64 [installed] postgresql-16-pgtap/jammy-pgdg,now 1.3.3-1.pgdg22.04+1 all [installed] postgresql-16-unit/jammy-pgdg,now 7.8-1.pgdg22.04+1 amd64 [installed] postgresql-16/jammy-pgdg,now 16.2-1.pgdg22.04+1 amd64 [installed,automatic] postgresql-client-14/jammy-pgdg,now 14.11-1.pgdg22.04+1 amd64 [installed,automatic] postgresql-client-15/jammy-pgdg,now 15.6-1.pgdg22.04+1 amd64 [installed,automatic] postgresql-client-16/jammy-pgdg,now 16.2-1.pgdg22.04+1 amd64 [installed,automatic] postgresql-client-common/jammy-pgdg,now 259.pgdg22.04+1 all [installed,automatic] postgresql-common/jammy-pgdg,now 259.pgdg22.04+1 all [installed,automatic] postgresql-plpython3-14/jammy-pgdg,now 14.11-1.pgdg22.04+1 amd64 [installed] postgresql-plpython3-15/jammy-pgdg,now 15.6-1.pgdg22.04+1 amd64 [installed] postgresql-plpython3-16/jammy-pgdg,now 16.2-1.pgdg22.04+1 amd64 [installed] postgresql-server-dev-16/jammy-pgdg,now 16.2-1.pgdg22.04+1 amd64 [installed] postgresql/jammy-pgdg,now 16+259.pgdg22.04+1 all [installed] > > Could I get some help on how to do that? > Are the old build processes documented somewhere? Or are there some > scripts in a far corner of the Internet that could still do that? As to Apt build scripts: https://wiki.postgresql.org/wiki/Apt/RepoDocs > > Or what options might I need to pass to ./configure to get it to build > with relative locations? > I'm not a C developer, and I'm not familiar with C build tools beyond > |./configure; make; sudo make install|​. > > I'd really appreciate some direction on this. Thanks. > > AJ ONeal -- Adrian Klaver adrian.klaver@aklaver.com