| From: | "David E(dot) Wheeler" <david(at)justatheory(dot)com> |
|---|---|
| To: | Paul Ramsey <pramsey(at)cleverelephant(dot)ca> |
| Cc: | PostgreSQL Hackers <pgsql-hackers(at)postgresql(dot)org>, Gabriele Bartolini <gabriele(dot)bartolini(at)enterprisedb(dot)com>, Peter Eisentraut <peter(at)eisentraut(dot)org>, Christoph Berg <myon(at)debian(dot)org>, Andres Freund <andres(at)anarazel(dot)de> |
| Subject: | Re: RFC: Extension Packaging & Lookup |
| Date: | 2024-10-29 17:16:21 |
| Message-ID: | EECDF53A-11B9-4F2F-A4C1-7F03078A3179@justatheory.com |
| Views: | Raw Message | Whole Thread | Download mbox | Resend email |
| Thread: | |
| Lists: | pgsql-hackers |
On Oct 29, 2024, at 12:23, Paul Ramsey <pramsey(at)cleverelephant(dot)ca> wrote:
> Question for the more knowledgable, how are binary distribution systems like Conda and others shipping DLLs such that different packages don’t clobber each other?
I’m not familiar with Conda, but from its docs[1], it seems to rely on a value compiled into an app:
> * On Linux, the $ORIGIN variable allows you to specify "relative to this file as it is being executed".
> * On macOS, the variables are:
> * @rpath---Allows you to set relative links from the system load paths.
> * @loader_path---Equivalent to $ORIGIN.
> * @executable_path---Supports the Apple .app directory approach, where libraries know where they live relative to their calling application.
Thinks are a bit more complicated on Windows, which doesn’t support something like -rpath.
D
[1]: https://docs.conda.io/projects/conda-build/en/latest/resources/use-shared-libraries.html
| From | Date | Subject | |
|---|---|---|---|
| Next Message | Paul Ramsey | 2024-10-29 17:16:54 | Re: RFC: Extension Packaging & Lookup |
| Previous Message | Jacob Champion | 2024-10-29 17:15:20 | Re: Support LIKE with nondeterministic collations |