The question: I installed a program by getting its source code, and then running `sudo make install`; how to make `apt-get` know about it?
The edit that was removed: (revision history here)
Edit for posterity:
As the top answer suggests, checkinstall
should be used whenever possible instead of make install
. checkinstall
is really nifty, since it follows what the make install
command would do, in order to figure out how to build a package.
This means that if you install a program using make install
, but then want to repent for your sins, all you have to do is sudo checkinstall -D make install
, and that command will:
follow
make install
to figure out what it doescopy-cat
make install
, except in *.deb package forminstall from the package (exactly as
make install
would have, given point 1)) except also letapt-get
know about it, and thus overwrite all the files exactly wheremake install
would have put them as long as you choose YES to include the files put bymake install
in the home directory in the package as well -- a couple of options during thecheckinstall
process will let you choose (obviously though, the choice is there so you can exercise it on a case-to-case basis)
Bonus: you can also remove a package (call it progA
again) installed using make install
that odes not have make uninstall
support by following the checkinstall
process outlined so far, and then simply doing:
dpkg -r progA
As far as I can see, there are no reasons given as to why the edit was made, and...to be honest, the edit is kind of a big deal to me, since I feel like I learned something important (I have faced problems with vanilla make install
more than once before, and MOST instructions for building from source talk about using make install
, NOT checkinstall
).
I am trying not to be annoyed (but this is irritating just because it's erasing effort I have put in for my own sake), so can someone help me figure out what's going on?