Uninstalling Homebrew - homebrew

I uninstalled Homebrew on my MAC, but got this message at the end:
The following possible Homebrew files were not deleted:
/opt/homebrew/SECURITY.md
/opt/homebrew/etc/
/opt/homebrew/share/
/opt/homebrew/var/
You may wish to remove them yourself.
I was able to remove the first item, but when I tried to remove the remaining three with "rmdir," I kept getting the "_____ is a directory" output. What am I missing?
Thanks.

Apparently, rmdir only works if the directory is empty, looking at this linux man page. You could try to remove them using rm -rf <path to folder> instead.

Maybe not an answer, but seems these folder are left on purpose. They are not part of the Homebrew package manager itself. But config, file, cache, etc content generated by brew-installed package.
Especially, make sure you have a backup of these settings before you remove it with rm -rf.

Related

I install a python package with "pip install opencv-python" and it gives me a warning in Ubuntu

The warning it gives me is this:
WARNING: The scripts f2py, f2py3 and f2py3.10 are installed in '/home/minombre/.local/bin' which is not on PATH.
Consider adding this directory to PATH or, if you prefer to suppress this warning, use --no-warn-script-location.
How do I fix this?
Or can I just leave it like that?
even though I would like to fix it.
I am using for the first time linux ubuntu.
The warning message you are seeing is telling you that the scripts 'f2py', 'f2py3', and 'f2py3.10' are installed in the directory '/home/minombre/.local/bin', but this directory is not on your system's PATH. The PATH is a list of directories that your system looks in when you run a command. When you run a command, your system looks in the directories listed in the PATH for a file with that name.
You have a few options to solve this:
Add the directory '/home/minombre/.local/bin' to your system's PATH. This will allow your system to find the scripts when you run them. You can do this by editing the '.bashrc' file in your home directory and adding the following line at the end of the file:
export PATH=$PATH:/home/minombre/.local/bin
Use the full path to the script when you run it. Instead of just
running f2py, for example, you would run
'/home/minombre/.local/bin/f2py'
Use the '--no-warn-script-location' flag when you install the package.
This will suppress the warning message but it will not add the
directory to your PATH.
pip install opencv-python --no-warn-script-location
It's important to note that if you are not going to use the scripts that are giving the warning, you can safely ignore the warning.
It is also important to mention that you can also check your PATH by running in the terminal:
echo $PATH
and it will show you the list of directories.

How to revert Homebrew to a previous state after an update

I installed an app, which triggered an update of Homebrew and apparently also of some apps. Now I am unable to get some apps running, for example MySQL.
Some apps complain about not finding libicuuc.70.dylib after icu4c71.1 has been apparently installed by the update cycle.
I would like to revert the whole Homebrew installation to the point before the update was triggered to get my apps running again and to find out what went wrong. I can rely on TimeMachine.
Which directories do I have to replace through a backup?
I have the following directories in /usr/local :
/usr/local/bin
/usr/local/Caskroom
/usr/local/Cellar
/usr/local/etc
/usr/local/Frameworks
/usr/local/Homebrew
/usr/local/include
/usr/local/lib
/usr/local/opt
/usr/local/remotedesktop
/usr/local/sbin
/usr/local/share
/usr/local/var
At the end I resorted to restoring the complete /usr/local directory from a Timemachine backup and got all homebrew installed applications running again.
I did the following:
delete the content in /usr/local.
enter Time Machine and go to a specific time in the past, where the system was still running
selected all the files and directories and restored them
The var directory gets generated automatically by the system, once it is deleted, but it there where no conflicts. At first I tried to restore with out deleting the content of /usr/local before restoring it, but I got an error and the restore did not complete. After deleting it before the restore everything went through.
I still do not know what broke my system and would like to know more about Homebrew. In the time I am using homebrew it changed a lot the way it works and consequently my experience and the unexpected results I get sometimes.

ethermint: command not found, When attempting ethermint installation?

I'm following the steps to install ethermint on top of tendermint that are listed on the README on this github page: https://github.com/tendermint/ethermint, but at the step ethermint --datadir ~/.ethermint init setup/genesis.json, then I get the following error: ethermint: command not found
And yes, I installed tendermint previous to my attempted installation of ethermint.
While the solution I figured out for my problem is contained on the GitHub issue page linked above, I also wanted to include it here for the sake of people who have the same issue.
OK, so I fixed the problem, and it was so infuriating. It turns out
that whenever I opened a terminal, then the go version would default
to go1.6, even if I was in the go1.8.3 directory. To solve the error,
you need to delete the old go version off of your computer, and then
use gvm to set the right go version. Thanks to everyone who helped me
solve this issue.
Check your current directory:
ls
if ethermint doesn't exist you need to install it again

Has /usr/local/Library/Contributions/ been deprecated?

For some time I've had a
/usr/local/Library/Contributions/
directory on my system and have been loading at least a brew_bash_completion.sh from it with
source $(brew --repository)/Library/Contributions/brew_bash_completion.sh
in my .bash_profile.
But suddenly I have no /usr/local/Library/Contributions/ directory at all!
Has this directory been moved or deprecated by Homebrew? What is the current best way to get support for brew bash completion?
The Homebrew completion script is at /usr/local/etc/bash_completion.d/brew (or, more generally, $(brew --prefix)/etc/bash_completion.d/brew). This change was made on April 3rd in commit edf000e when some parts of Homebrew were re-organized.

Downloading JUST the iOS Facebook SDK, not the freaky package?

We all love the Facebook SDK for iOS, if you go here to download it,
https://developers.facebook.com/docs/ios/getting-started
for some reason you get this sort of insane .pkg file,
which APPEARS TO ONLY create the "FacebookSDK" folder in your "Documents" folder.
Then you just move it where you want, wondering "Why the hell do they do that?"
Does anyone know
Is there on Facebook.com an official link somewhere to simply a zip of the library?
Is there a reason they use the package system? (Does it -- check on versions, or something - does it check you have needed stuff on your Mac maybe?)
Does it drop any crap anywhere that one has to clean up? Is it mildly malicious at all?
The installer also installs the docset.
You can check in Terminal to see what's going on:
First, expand the installer from inside your Downloads directory:
$ mkdir facebook_sdk
$ cd facebook_sdk
$ xar -xf ../facebook-ios-sdk-3.15.1.pkg
This will create a new pkg file which is just a directory. cd into that and unzip the Payload:
$ cd FacebookSDK.pkg
$ cat Payload | gunzip -dc |cpio -i
Then open the directory in Finder to browse the contents:
$ open -a finder .
You'll be able to see what gets copied where, and you can just pull out whatever you want:
To answer your questions more specifically:
Is there on Facebook.com an official link somewhere to simply a zip of the library?
To my knowledge, no, but you can use CocoaPods to get it.
Is there a reason they use the package system? (Does it -- check on versions, or something - does it check you have needed stuff on your Mac maybe?)
It might remove old deprecated files when installing new versions, and it makes it easier to install the docs.
Does it drop any crap anywhere that one has to clean up? Is it mildly malicious at all?
It's not malicious. You might not want the docs if you're tight on space.

Resources