Re: pgsql: oauth: Move the builtin flow into a separate module

2025-05-01 Thread Jacob Champion
On Thu, May 1, 2025 at 10:48 AM Tom Lane wrote: > It looks like you need to mention libintl explicitly in the link > command for libpq-oauth, if we're building with NLS. > macOS is picky that way ... Yeah, and that was in at one point at Peter's suggestion. :/ I made the mistake of taking it back

Re: pgsql: oauth: Move the builtin flow into a separate module

2025-05-01 Thread Tom Lane
Jacob Champion writes: > I'm taking a look at the MacPorts failure now. It looks like you need to mention libintl explicitly in the link command for libpq-oauth, if we're building with NLS. macOS is picky that way ... regards, tom lane

Re: pgsql: oauth: Move the builtin flow into a separate module

2025-05-01 Thread Jacob Champion
On Thu, May 1, 2025 at 10:26 AM Jacob Champion wrote: > > oauth: Move the builtin flow into a separate module I'm taking a look at the MacPorts failure now. --Jacob

pgsql: oauth: Move the builtin flow into a separate module

2025-05-01 Thread Jacob Champion
oauth: Move the builtin flow into a separate module The additional packaging footprint of the OAuth Curl dependency, as well as the existence of libcurl in the address space even if OAuth isn't ever used by a client, has raised some concerns. Split off this dependency into a separate loadable modu