Resolving dependencies

Calcutec · 09-08-2002, 01:33 PM

I am attempting to install ripperX (rpm) under Slack 8.1. I have tried both kpackage and rpm -i from the command line (and pkgtool, which just craps out after the first menu for some reason).

Under both methods I am informed of many dependencies. All of the other packages are installed, however. How can I make the ripperX rpm aware of this fact? The kpackage guide notes that a package.txt file can be used in slack, but I do not have such a file on my system.

Thanks.

NSKL · 09-08-2002, 01:50 PM

Uhm, its a very bad idea to try installing RPMs in Slack, but slack comes with a neat tool called rpm2tgz. Run rpm2tgz on ripperX rpm and then you'll get a .tgz package, just install it with installpkg. If that doesnt work (it should but just in case) download ripperX source and compile it, its way better.
Hope that helps
-NSKL

Calcutec · 09-08-2002, 02:45 PM

Thank you. I just downloaded the tarball and installed that way. As cool as rpm2tgz may be, is there really anything out there that you can't get as a tarball?

neo77777 · 09-08-2002, 02:58 PM

Yep, MS Windows Operating *cough* System *cough*

, at least officially you can't.

MasterC · 09-08-2002, 03:21 PM

Well, I would venture a guess at a very HUGE list of things you can't get as a tarball, but then when you put filters like: can run on most linux boxes, then you would shorten my list down to almost zilch.

For example, I don't think I have ever seen an actual physical McLaren F1 in a tarball

Cool