Author Topic: What is the "correct" way to install self-compiled binaries?  (Read 530 times)

asdf

  • Member
  • **
  • Posts: 51
  • Kudos: 0
I use Debian, and apt is working great with me. I used to use Red Hat, and the RPM stuff was OK but the dependency hell really aggravated me. Anyway, I was wondering if there was a traditional way of installing and managing things you compile yourself (for things that aren't pre-compiled, or things you just want to compile by yourself).

Take wine for example. Is there a preferred method of doing this? I unpacked the source into my home directory and compiled it. I then did a 'make install' as root. I deleted the source, and kept the Makefile (so I can easily 'make uninstall' when I want to). I figured that would work, but it seems kinda unconventional.

Is there a convention for this? If so, what is it?

voidmain

  • VIP
  • Member
  • ***
  • Posts: 5,605
  • Kudos: 184
    • http://voidmain.is-a-geek.net/
About the only way to get similar package management as you get with *.deb packages or *.rpm package is to turn your package into a *.deb package or an *.rpm package. There are howtos on how to do this. This is really the only answer other than if the Makefile has an "uninstall" section.  However, even if it did you would have to reinstall the source in order to do the "make uninstall", not pretty, but that's the way it is.
Someone please remove this account. Thanks...