I had to compile subversion from ports to enable SASL. Now when I run "pkg upgrade", pkg wants to re-install subversion. I think this is not what I want. I've (re)read chapter 4 of the handbook. I am looking for a way to not have pkg overwrite my SASL enabled subversion.
pkg lock package_name and your package will not be modified or deleted. The only downside is that you have to upgrade manually your package.
Also just as an advice: don't mix packages with ports you will end up breaking your system. Use ports-mgmt/poudriere or ports-mgmt/synth to build custom packages.
I've seen the "don't mix" warning repeated here many times. This is not realistic for this situation. This is the only port needed. Everything else is a binary package. It is not practical for me to run a build server to re-compile my entire userland because of one port. Since you called this out, I'd love to hear how others cope with this.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
