:: 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’d say generally you’re right to keep them so that you don’t have to install them again on updates. depends on how heavy the dependencies are, how often you update, if you’re planning on removing the package soon, etc. it’s gonna be tough to make a recommendation without knowing your situation, but for me personally i’d be on the lookout for a binary distribution or other more efficient install options. barring other options i’d probably keep them as long as they aren’t overriding another system library.