switching from ports to pkg -- mailman group mismatch

[David Benfell]

On Thu, Dec 04, 2014 at 01:23:51PM -0800, Darren Pilgrim wrote:
> 
> That likely means mailman assumes there's a sendmail program it can use 
> for mail injection.  Does it "just work" if you tell postfix to activate 
> itself in mailer.conf?
> 
Postfix is already selected in mailer.conf. Apparently postfix's
sendmail is not a substitute for the real sendmail in mailman unless
it is configured and built with postfix selected.

> It's fine to mix them.  I have a handful of ports on everyt system I 
> have to compile myself--mostly because I want them linked to the ports 
> OpenSSL, but there are some that need non-default values.  I just keep 
> them locked so a pkg-upgrade doesn't touch them.
> 
> If you end up with a lot of compiled ports, set up poudrerie.

I will look into this. At the moment, I only have mailman that I know
*must* be built from the port.

> 
> Where did you see this advice?  About all that happens is pkg will 
> report "options changed" and want to reinstall it from the package. 
> Pkg-lock is your friend.

Yes, I must look into pkg lock. I believe the advice about sticking
with default options was on this list in response to someone else
having trouble with ports. This is where, perhaps, my desire for ports
where all the options work is unsustainable: The work of maintaining a
port must expand, probably more than exponentially, if all
combinations of options must be tested.

Thanks!
-- 
David Benfell <benfell at parts-unknown.org>
See https://parts-unknown.org/node/2 if you don't understand the
attachment.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 819 bytes
Desc: not available
URL: <http://lists.freebsd.org/pipermail/freebsd-questions/attachments/20141204/35de4542/attachment.sig>