"It depends".
# pkg install -f ./myPackage.pkg). # make config, if these differ from the standard then you could run into a heap of trouble. And that's just mentioning the most obvious example... what about your port being build against (say) DB3 while the binary package used DB8?And this is why I said the above.
I think portmaster is also on the way out.
where have you heard it?
make config. I think that's old news. There was a small period where Portmaster didn't have a port maintainer and I believe that's when things started to turn towards port removal. However, nowadays it has a new maintainer and the script continues to work perfectly.I've read it is various places including these forums, but an "official" example would be this:
FreeBSD 13.4-RELEASE Release Notes
FreeBSD is an operating system used to power modern servers, desktops, and embedded platforms.www.freebsd.org
Go down to Packaging section (right near the end):
ports-mgmt/portmaster has been removed as it has been discouraged in favour of using pkg and binary packages.
I have a few custom ports that have different build options to those of the standard packages. I use Poudriere to compile them and create the corresponding binary packages that are saved on my private package repo for automatic distribution where needed. I haven't built a port locally on my workstation since I have been using Poudriere, which is probably ten years.
portupgrade is abandoned software.
Did you set/unset options on those ports? If not, then there's really no point in building from ports in the first place. If you did customize the options then installing the package would 'reset' those. The packages in the FreeBSD repositories are all built with their default options.
Some ports are not available as binary packages due to licensing issues.
yes of coarse I did that's the whole point of using ports! and also have more recent software and patch
Well if you track "latest" in packages, the difference should be only a couple of days max (assuming that you build ports every day).
The pain point for me was more things pulling in rust (or an older llvm) as a build dependency. I think there are ways around that (e.g. use pkg for installing rust) but at that point it felt too complicated and there was the push against portmaster. So I've moved to binary packages for now but good to know portmaster is still there if I need to go back to it.
But that isn't something which Portmaster decides on its own, things like this happen because such environments are part of the build dependencies for some ports. Something which you can check for by running
make build-depends-list. This is also why there are differences between build an run dependencies.That's of course possible, but there's always a certain risk involved when you mix ports and packages.
# Check for ports to ignore.
for a in $(cat $CONF | grep -e '^ignore' | cut -d '=' -f2-); do
if [ ! -z $a ]; then IGNORE="$IGNORE -x $a"; fi
done;
<snip>
build() {
portmaster -a $IGNORE\
| tee $LOG
}