1

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?

Gilles 'SO- stop being evil'
  • 807,993
  • 194
  • 1,674
  • 2,175
Scribblemacher
  • 193
  • 8
  • 4
    Look at CheckInstall: https://wiki.debian.org/CheckInstall – jasonwryan Mar 16 '16 at 02:14
  • 1
    Another option is to install it under a prefix like `/usr/local/` or `/opt/`. You'll have to modify some environment variables like PATH to get it work though, but the advantage is you know exactly what is installed by the package. – Munir Mar 16 '16 at 02:55
  • Related: [This post](https://unix.stackexchange.com/q/202371/125388) had asked on "How to manage Debian source code packages using aptitude or apt?", which had an answer for using `apt-src`. Just one of the ways, but may be not the best. –  Mar 16 '16 at 04:20
  • also look at `dh-make` and/or `debhelper` - tools that make it easy to build a package from unpackaged source code. – cas Mar 16 '16 at 20:56

0 Answers0