packages vs ports, do they conflict?

Dale Scott dalescott at
Wed Dec 19 06:37:01 UTC 2018

So long as you don’t change the configuration defaults it probably won’t make a difference, and the eventual install of any dependencies already installed should fail gracefully. Maybe...  I’m also not sure if default port configs are guaranteed to be the same configs used to build pkgs though. 

I have to install a couple apps on my server from ports because of non-default configuration options that are needed. I flag them in pkg to leave alone when I “pkg upgrade”, then I update them manually. It might be a bigger deal if I had lots of apps to install as ports, or lots of servers, but it’s ok as-is for me.


> On Dec 18, 2018, at 9:54 PM, Ian Zimmerman <itz at> wrote:
> I just tried to compile a port for the first time, and I tried to follow
> the Handbook as closely as possible, as is fitting for a newbie.  So,
> after becoming root in the port directory, the first thing I tried was
> "make config-recursive".  And the first dialog of options was for bash.
> So I guess this port has the bash port as a dependency.  But I have
> already installed bash as a package!  If I go ahead with the build, will
> a bash port be built and installed too, overwriting the package
> installation - maybe with different and undesirable options?  How does
> this work in general?  Can I mix packages and ports at all, or do I have
> to commit to one framework or the other for all software installs?
> Thanks for clarifications.
> -- 
> Please don't Cc: me privately on mailing lists and Usenet,
> if you also post the followup to the list or newsgroup.
> To reply privately _only_ on Usenet and on broken lists
> which rewrite From, fetch the TXT record for
> _______________________________________________
> freebsd-questions at mailing list
> To unsubscribe, send any mail to "freebsd-questions-unsubscribe at"

More information about the freebsd-questions mailing list