Date: Sat, 04 May 2024 00:12:55 +0000
To: "pgsql-general@lists.postgresql.org" <pgsql-general@lists.postgresql.org>
From: AJ ONeal <coolaj86@proton.me>
Subject: Re: How to Build Postgres in a Portable / Relocatable fashion?
Message-ID: <UsfgvLLt8VkL8nBwR4MDOqw89Y6OChvbXDoOWn74C3zNMByBOY9UPG8W_lWN8c2eEPut4svGmCAX4_82oZfC87gISSMp2jhctSkeMejgwAw=@proton.me>
In-Reply-To: <2770930.1714779894@sss.pgh.pa.us>
References: <v_-p47epUmnjcXPhpH9dygB6PKkwhLsccfj7o0snGd-GNubV138HZaU1YvAcyoqeQ4pqcT20hgHbmVlwaYXpcWDZ_iDCREz1A8hkkEDYdF8=@proton.me> <f07765c7-b42b-4339-8044-c7b10d81b436@aklaver.com> <rjf-sGbM2HPV0EZuoN9yA4GDL9CqVCD2AzkwyByjKmF5mGstw6TrqT_5OIC1yPvfSAsjyE30Y4i4Oojq5nwQXtjdFVF7dx0cXxJgSBARBV8=@proton.me> <2770930.1714779894@sss.pgh.pa.us>
Feedback-ID: 64821478:user:proton
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
Archived-At: <https://www.postgresql.org/message-id/UsfgvLLt8VkL8nBwR4MDOqw89Y6OChvbXDoOWn74C3zNMByBOY9UPG8W_lWN8c2eEPut4svGmCAX4_82oZfC87gISSMp2jhctSkeMejgwAw%3D%40proton.me>
Precedence: bulk


> > What I want to create (and provide) is a portable tarball that has
> > most of all what it needs in the tarball and will look for relevant
> > libraries relative to itself.
>=20
>=20
> See
>=20
> https://www.postgresql.org/docs/current/installation.html
>=20
> particularly the discussion of installation relocatability under
>=20
> https://www.postgresql.org/docs/current/install-make.html#CONFIGURE-OPTIO=
NS-LOCATIONS

It seems like the first bit of magic I need is:
`--prefix=3D/doesntexist/postgres`

Including 'postgres' as part of the name puts it in "relative mode", so-to-=
speak.

Thank you!

> > Something that Just Works=E2=84=A2 almost anywhere (Ubuntu, Debian, Red=
Hat, Suse... maybe even Alpine).
>=20
>=20
> That's a little harder, mainly because the shared libraries for
> dependencies like openssl etc may not be 100% compatible across
> all those platforms. Different versions, different build options,
> yadda yadda.

I'd like to build as much static as possible (or reasonable). Is there a wa=
y to tell it "just include openssl"?

> Maybe you should be thinking in terms of a docker container
> or the like?

I really hate Docker. The idea of "we can't ship your computer to the clien=
t, so we'll just ship... a clone of you computer to the client" offends my =
sensibilities.

Or rather, I like the opportunity that LXC provides in the right context, b=
ut I don't like how it's become a replacement for shared knowledge within a=
 group - i.e. "no one can remember the wisdom of the ancients, so if this f=
ragile system that Ted built ever fails or needs a change no one knows how =
he did it or what the options mean, but don't worry, it's all encapsulated =
in a very complex Dockerfile that no one understands and depends on hundred=
s of layers of images... but it's not like someone would ever leftpad any o=
f them... What could go wrong?"