installpkg

va3dxs · 04-10-2006, 11:45 PM

This is not a request for help, but I am interested to know:

If I install a new package using installpkg it takes a few seconds.

If I install a new package using the five step approach it takes a l o n g time.

Why?

jong357 · 04-10-2006, 11:57 PM

What's the five step approach?

I must be out of the loop...

va3dxs · 04-11-2006, 12:02 AM

Well I think it is:

tar xvzf package.tgz
cd package
./configure
make
make install

edavis · 04-11-2006, 12:57 AM

That's because when you install with installpkg you are only installing the necessary files that come with the package. With your five step approach you have to do the time consuming task of compiling all the source code before you can get a final product.

Alien_Hominid · 04-11-2006, 01:22 AM

You could get the Slackware package with checkinstall (run checkinstall rather than make install and it will make package for you). Then you could install this package running installpkg. Checkinstall can be found in the extra directory on your cd (it's not installed by default).

va3dxs · 04-11-2006, 11:56 AM

Thanks for the information - I like to learn a little!

bird603568 · 04-11-2006, 01:20 PM

Quote:

Originally Posted by va3dxs

Well I think it is:

tar xvzf package.tgz
cd package
./configure
make
make install

you shouldn't be able to compile a package. do you mean .tar.gz?

va3dxs · 04-11-2006, 02:17 PM

Well no. My understanding is that .tar.gz and .tgz are the same thing? What I have done is if it is a specifically Slackware package I use installpkg. Otherwise I have gone through the whole routine. It's always worked with both .tgz and .tar.gz packages. And that incidentally is why I like Slackware so much - it always works if the dependencies are satisfied. That was very far from the case with the other 'easier' distros I tried.

va3dxs · 04-11-2006, 02:21 PM

Let me just clarify that last post. I try to follow the instructions for each particular package! Sometimes the ./configure step is not necessary, and so on.

merchtemeagle · 04-11-2006, 04:51 PM

Quote:

Originally Posted by va3dxs

Well no. My understanding is that .tar.gz and .tgz are the same thing? What I have done is if it is a specifically Slackware package I use installpkg. Otherwise I have gone through the whole routine. It's always worked with both .tgz and .tar.gz packages. And that incidentally is why I like Slackware so much - it always works if the dependencies are satisfied. That was very far from the case with the other 'easier' distros I tried.

Both are just compressed data. A Slackware package is never compressed as .tar.gz as far as I know, .tgz could be a package as well as a source tarball. You'll have to make sure when you download it whether it is a package or source files which need to be compiled. (that's what ./configure, make does)

va3dxs · 04-11-2006, 07:11 PM

OK - thanks

Relieved to know that my understanding of the situation was correct! And yes, I believe you are right to say that Slackware packages are always .tgz.