Personally, whenever I log in, I've got a dual core with lots of memory, so I don't generally notice any drop in performance when I'm compiling things.
Updates have the possibility of bringing a new set of bugs into your environment. If the package is not vulnerable or you don't need any additional functionality then I don't see any plausible reason to update it.
I frequently check freshports, there's a list of "new 7 days" or "new 48 hours". When something interesting pops up or when enough ports are out of date I rebuild everything.
I update ports tree every day, but i only update ports if there is major version change (1.1 to 1.2, and don't update any 1.1.1 to any 1.1.x unless i really need to)
On my single core machine I do binary updates with pkg_upgrade, but the index for the 7-stable packages hasn't been updated in almost a month, so there's nothing to update. I'm starting to wonder whether 7-stable packages have been abandoned.
Ports: daily, OS: monthly. On everything I can get my hands on. Bugs? Maybe ten in fifteen years? Fatal ones? Nothing a re-csup or a re-portsnap couldn't handle.
On my single core machine I do binary updates with pkg_upgrade, but the index for the 7-stable packages hasn't been updated in almost a month, so there's nothing to update. I'm starting to wonder whether 7-stable packages have been abandoned.
Not really, but I guess my perception is coloured by the fact that I used portupgrade -PP to handle binary package upgrades (which uses a fresh ports tree to compare versions).
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.
