4 ms·

That's a very good reason to only install apps with a real package installer. On OSX, this is a no-brainer with brew[1] and brew cask[2] # On my old mac $

That's a very good reason to only install apps with a real package installer. On OSX, this is a no-brainer with brew[1] and brew cask[2] # On my old mac $ brew list $ brew cask list => then I save relevant parts for future references brew install npm brew install zsh brew cask install sublime-text brew cask install google-chrome brew cask install intellij-idea [1] http://brew.sh/ http://brew.sh/ [2] https://caskroom.github.io/ https://caskroom.github.io/

desdiv 10y ago
>brew list Protip: "brew list" will list all installed packages, including dependencies, which you might not want. What you probably want is "brew leaves", where it lists all installed packages that are not dependencies of another installed package. This makes a difference in cases where a dependency is no longer needed in the latest version. On a related note, why does the majority of package managers make the common and simple task of "list all manually installed packages" so incredibly hard? For a fun brain twister, try to list all the manually installed packages on your system by just reading the man pages and no internet. Ubuntu is nightmare mode for this challenge.
- benwaffle 10y ago
  On arch, looks like this will do: pacman -Qe
- jmiserez 10y ago
  For Ubuntu, look no further: http://askubuntu.com/a/492343/145754 http://askubuntu.com/a/492343/145754
stephenr 10y ago
> real package installer > brew That right there is irony. You intended to give good advice about using reliable methods for installing software, then immediately recommend the Devils ass crack of package management tools.