You can cat the Makefile and read what the install process actually does. Just look for the install section. Also, some software will allow you to specify a destination directory to install to. This is usually specified in an option during "make install". Finally, if nothing else you can sometimes change the install directories by setting options during "./configure".

For example, when using the option at "make install" it looks like
If that is not available you can usually set PREFIX during the configure process (by default it is usually something like /usr so include 'usr' at the end if you change this to a test directory).

You might want to change other env vars during configure as well. To see the available options do this

When you set the install directory or PREFIX everything should get installed to that directory tree. All that will be left to create a Slackware package is to add a description (slack-desc) and then run makepkg!

This is essentially the process that most Slackbuilds use. Take a look at http://slackwiki.org/Writing_A_Slack..._Not_Available. That page tells you everything you need to know about Slackware package creation. The particular section the link points to goes into more detail about what you can do if there is no DESTDIR option. I suggest you take a look at some of the Slackbuild scripts (search at http://slackbuilds.org/) for software you use. After reading them and that wiki page you should have a good idea how this process works.

If the software you are trying to install doesn't use configure or even a Makefile at all it might not need to be installed (or you have to manually move files to install it) or it includes a script to do the work. Try reading the script. Does it have an uninstall routine? Is is made for Slackware or distros like Fedora/Red Hat or Debian/Ubuntu? Does it give you any destination directory options?

If you are still stuck you can try out src2pkg. For those of you thinking about checkinstall read this thread about checkinstall. Basically this program watches changes to your system during the install routine and makes a package out of it. The software does not get installed until you install the new package. This program is not perfect and you might need to tweak some settings once in a while.

Another thing you can do is set up a clean virtual test box using vmware. Simply install your software and note the changes to the system. When you are done revert to a snapshot.

Finally, always read ALL the documentation that comes with software and in particular any README or INSTALL files. Sometimes you find out things that could save you a lot of hassle.

Hi,

In response to your post about 'PREFIX' and 'DESTDIR=', I refer you to a post by gnashley (src2pkg author). A great definition to a query about src2pkg!

As for checkinstall, I quit using it with Slackware 12, even with the option 'fstrans=no' flag. I wondered about some of issues before , now with gnashley's explanation things are better.

Definitely a good read... including the article on linux.com (http://www.linux.com/feature/121499).

Hi Shadowsnipes,

I think you have read my mind:

Makes me want to never run X ever again :-)

Andrew

Haha, the funny thing is that even though I use X a lot I usually only use it for Firefox, Audacious, Mousepad, and Battle for Wesnoth. However, I use pico more than Mousepad, I use herrie (an excellent ncurses playlist player) almost as much as Audacious, and I use lynx at least every week. Now only if there was a ncurses version of BfW I would be all set!

The REAL funny thing is that I often use those CL programs while I am still using X (often while playing BfW in fullscreen - good ole tty6)!

Yes. Same here. For me, Slackware was only the second distro that I tried. Now I'm stuck in the Slackware groove and can't switch to anything else. Everything else just feels unnatural, uncomfortable, slow and unresponsive.

I been Slackin' since 1999...

"You can check-out any time you like,
but you can never leave..." BWAHAHAHAHAHA

How can one not notice ? A good example would be Ubuntu, with their little corner pop-ups telling you there's updates found, just like in Window$.

I personally think your dream is a vision of the future (as some dreams can be) ... sad, but unfortunately quite likely

But, really that's only one possible path the future can take ... I hope it will not be the one.