Me: "I'm quite happy with my ancient 2012 Mac mini. It does everything I want and since I'm not doing video processing or anything resource intensive, it's fine for me."
Also me: "Gee, I see I haven't done a 'brew update' in awhile."
hours later and brew update is still running while maxing out my CPU
@jann I used to use MacPorts many years ago. I don't remember why I switched, although I do remember I had problems with it back then; I just don't remember what they were.
@jann brew reminds me that "if it ain't broke, don't fix it" but when I do need an update, I better be prepared for a long wait. My scripts are failing now because my python got updated, but it doesn't copy over the modules not part of the base install that I've downloaded in the old version. But I can't install them now until the brew update completes. Sigh.
@TWSheppard Whoa! At least my python modules are all updated during the python update under MacPorts. Whew! (Same w/perl, etc...that I know of. Wonder why it isn't the same w/brew!)
@jann It's definitely a major omission because I have to look in the old lib folder (which is a long, convoluted path) to find what I've downloaded and then manually reinstall them. Pretty dumb—I'm probably doing something wrong.
@TWSheppard I'll let you know if i find a simpler way. In MacPorts it's a simple: “port upgrade outdated”... but I'm not bragging...cos MacPorts sucks in other ways.
Add comment