Bsd updating repository catalogue

I required the nvidia-304 as the nvidia-375 auto-suppied by True OS and the nvidia-340 variants were not compatible with my HP laptop's graphics and didn't want to fall back on vesa.This was always a known problem for me in Linux - the nvidia-304* is a legacy option but has always worked in my HP G60.For a long time GNU/linux users have always used this as a reason not to use Free BSD and instead favour some GNU/linux combination with an all encompassing easy to use package manager, such as Debian’s apt-get.Free BSD’s response has always been, (not actual quote), “We have the ports collection, which is cooler and more flexible than just having some easy to use package manager.It may sound obvious, but before you start, you will need a binary package repository. Will try again before reporting, just in case there's something I'm missing to do. I'm now at a stage where I'm certain the old (*208 (??It was written with Free BSD in mind, but Dragon Fly BSD also supports pkgng.Maybe the other BSDs will adopt it as time goes on, too.

Free BSD has been long due a better package management system, pkg_add, pkg_info, etc just doesn’t cut it any more.

You can always do it yourself by writing scripts around the pkg_* tools or using portmaster’s –packages-only option”.

While this is all true, there is still a gap for a good package manager that needs filling.

) I'm hoping that by reading from tmp I'm doing the right thing. On issuing the most recent commands you suggest, sudo pc-updatemanager pkgcheck gives: Installed packages to be UPGRADED: Free BSD-examples: 12.0.s20170121141038 - 12.0.s20170205134406 [trueos-base] Seems that file never ever gets properly deleted for some reason.

I don't think rolling back a BE will help as every BE created has suffered with the same problem, from the very first, Yes, however this just takes me back to the beginning of my quest : )) I have only two extra packages installed on top of standard True OS: nvidia-304.* and xmms (audio player).