This question already has an answer here:
- Keeping track of programs 5 answers
Let's say that I've found a program that I want to install on my machine. It is only available as a source tarball that can be built with the usual ./configure; make; make install.
While I could do
make install in these instances, I'm likely not going to know where xyz file/command come from in a few years, and whether it is important. And who knows what will happen if I try to build a newer version of the program.
What's the most common, manageable way of handling scenarios like this?