Hello, and I apologize for my vague title.

Basically what I've done is I've been installing some files from source on Slackware because I am a bit shallow on hard drive space. It's because I'm using a 64GB SSD. I know the limited writes issue isn't too big of an issue anymore with modern SSD's, however I would still like to minimize the amount of writes I need to do.

Therefore, I have moved /tmp into my RAM disk as so:
I can successfully compile programs and not using up my SSD's writes by simply moving them to /tmp but installing them permanently to my computer is another situation.

Unfortunately my lack of knowledge and my 3 hours of Google search attempts fail me. So I come here as a last resort hoping somebody knows how to install packages to the computer itself. I'm confused as to how the .SlackBuild binaries create the .txz or .tgz files. I see the code:

So I"m assuming the makepkg does most of this for me, but my main concern is the code before the makepkg part as "makepkg" doesn't appear to work by itself.

The exception is flash player, I know I have to move libflashplayer.ko or whatever the file was called to the plugins section of my browser.

To install a package, you use installpkg:
It seems so simple that I must miss something

[edit]
I don't understand your first comment..
You install software from source in hope that it saves some space ?

I know how to install a package. However, what I'm trying to do is compile programs in RAM and then install them permanently whereas if I did everything in RAM the program installs in the RAM and would be deleted on a reboot.

On the other hand, if I use the *.SlackBuild files, even in /tmp which is placed in RAM, they install perfectly fine and work even on reboots. I'm trying to mimic that exact same process but I struggle with the /sbin/makepkg part as it creates the .tgz or .txz files for us which can then be managed with pkgtools. I'd like to do that too, is to create the .txz or .tgz files after I compile, but so far I'm struggling with that even after 3 hours of Google searching.

Scripts from SlackBuilds.org untar and compile packages in /tmp by default (unless you override it). Since you have your /tmp mounted as tmpfs, the whole package building process is already happening in RAM and nothing is written to your SSD. When SlackBuild finishes, you can installpkg or upgradepkg your freshly built package.txz (which also resides in /tmp) and move it to some permanent place (e.g. your home directory) for later use.

Well, the SlackBuild scripts also move all the results of compiling/installing your soon-to-be package to a single directory tree so that makepkg can actually work. Depending upon the source that you are building, that can be rather difficult to get exactly correct.

Have you looked at src2pkg?