I've been using FreeBSD for 8 months now and one thing bothers me the most is the 'pkg' package management.

it seems 'pkg' doesn't check all dependencies when install new application, unlike debian's 'apt'.

as a result, working applications usually become broken. as a example, most recently I installed 'awesome WM' on my thinkpad laptop, during the installation, it upgraded pkg sources, firefox, and bunch of other softwares. however, afterwards firefox, xfe, etc don't work anymore. I've searched web and it seems this is a common problem - in fact a deficiency of pkg. but surprisingly FreeBSD community (i.e. FreeBSD forum) seems ignore this serious problem.

The package manager for Slackware Linux also doesn't have dependency tracking. I think there are good reasons some package managers don't have that functions, though I'm not familiar with the philosophy behind it. I became used to, and learned Slackware, and had no problems once I understood some fundamentals. Some would suggest that if you are really that unhappy with a feature on your O/S, then it's time to switch. On the other hand, you may be able to find out why the package manager works like that, and adapt. Sometimes it's more a matter of personal preference than anything else.

1 members found this post helpful.

FreeBSD has exactly two methods of install a package: ports and pkg. and pkg does check dependency, albeit incomplete from my past experience. and I'd rather use pkg than compiling from ports to install a pkg. but given the often broken state of what 'pkg' usually does to my system, I'm really frustrated. of the pkg management tools I used in the past - 'apt' 'XBPS', pkg is the worst at doing dependency check. a quick look at github/FreeBSD pkg, one easily sees there are many unsolved issues with pkg.

one of the main reasons I use FreeBSD is to escape systemd.

You could try switching over to using ports.

I you run something like firefox in an xterm, what error message do you get?

Pkg only includes recommended and required dependencies for packages off the server.

If you want full coverage of all possible dependencies, you need to use the ports to create your own packages.