Re: pkg upgrade vs building from source

On Mon, Oct 10, 2022 at 6:02 AM Mel Pilgrim <list_freebsd@bluerosetech.com>
wrote:

> On 2022-10-09 14:10, paul beard wrote:
> >     The origin is the same for all three pkgs.  pkg info will show the
> >     flavour.  If you need cyrus support enabled, install the postfix-sasl
> >     pkg and see if you still get the error.
> >
> > It's the plain flavor.
> >
> > I don't see a -sasl variant…?
>
> You wouldn't.  Flavours don't have separate origins.
>
> > If you are referring to the make config dialog, no cyrus/sasl support
> > was added, just using the built-in dovecot support.
>
> The error messages in your original message come from enabling SASL in
> the smtp client without building with cyrus-sasl support.  Since, per
> your original message, that error went away when you switched from the
> public repo pkg back to your port build, that suggests the ports version
> has cyrus-sasl included.
>
> > no cyrus/sasl support was added, just using the built-in dovecot support.
>
> It's possible the postfix build process pulls in cyrus-sasl support if
> it's installed on the system at build time even when the port has SASL=off.
>
> With the working build installed, what are the outputs of the following
> commands:
>
> $ pkg options postfix
>

postfix - BDB: off
postfix - BLACKLISTD: on
postfix - CDB: off
postfix - DOCS: on
postfix - EAI: on
postfix - INST_BASE: off
postfix - LDAP: off
postfix - LMDB: off
postfix - MYSQL: off
postfix - NIS: off
postfix - PCRE2: on
postfix - PGSQL: off
postfix - SASL: off
postfix - SASLKMIT: off
postfix - SASLKRB5: off
postfix - SQLITE: off
postfix - TEST: on
postfix - TLS: on


> $ postconf -A
>
> postconf -A
cyrus

It all works now.

-- 
Paul Beard / www.paulbeard.org/