:: Remove make dependencies after install? [y/N] y
If I didn’t remove make dependencies, would yay/pacman be smart enough to know the thing I am installing does not actually depend on them? It’s a very nice feature of package managers that they track dependencies and can do things like remove “dangling” dependencies and I don’t want to mess that up with some random dependencies needed only for a build. But I also don’t want to install something every time I need to build lol.
So does yay and/or pacman know that the things I am installing don’t actually depend on the make dependencies?
Solution: Keeping the make dependencies after install will not fool pacman and/or yay into thinking the make dependencies are “real” dependencies of whatever you’re building from AUR. They both correctly recognize them as orphans (unless of course something else actually depends on them). So feel free to not remove them during install without worrying about dependency graphs getting tarnished; you’ll be able to easily remove them later if you’d like.
I think it is the equivalent of running ‘make clean’ after a build from source? You can do this manually building arch user repo packages to free up space because the executable and package that you installed is already there through pacman. However, updates in the future would require building those make dependencies again so it might save you time in the future, but probably irrelevant to you running the app today.
I’m most worried about having packages installed that my package manager thinks I intentionally installed and won’t auto remove. I’m not super into having a “minimal” system, so I don’t care if they sit around “unneeded”, but I want to make sure they’re gonna get removed if I remove the thing they were needed to build. Does that make sense?