Slackware - before I start....

[OliverW]

I have a question about slackware, before I download it and install it. What I read about Slackware makes clear that Slackware is not using any package system, and it wants me too compile software manually. I'm perfectly fine with that but what about dependencies? AFAIK tar.gz won't say that I'm missing something (some programs during make), but how is this resolved?

[Choozo]

Thats right, tar.gz won't say anything, because that is a compressed archive format ..... but ./configure will tell you if something is missing.

Cheers :)

[ 01 November 2001: Message edited by: Choozo ]

[Saptech]

I'm thinking of trying out Slack also.

Can you install the RPM's installer package and then use that to install rpm software?

[Choozo]

You may get into problems by doing so, since the RPM database then will know squat about the software already installed from sources, and thus give a lot of dependency 'errors'.

Just my thoughts about that, but maybe someone using Slack would know better? (They probably use Slack to get away from RPMs anyway, though.)
Cheers :)

[jaygee432]

Originally posted by Choozo:
[QB]maybe someone using Slack would know better QB]
At your service. First, it is not true that Slack does not have a package system. It uses .tgz packages, and they are very easy to install with an app called installpkg, and pkgtool can be used as a simple package manager. You can install rpms or convert them to .tgz format with something called rmp2tgz. I understand that dependencies can trip you up if you try to install rpms, but I've never had a problem. But then I've never messed with rpms in slack, because I've always been able to do what I wanted with .tgzs or tar.gzs or such. There is good documentation for all this and much more at www.slackware.com (http://www.slackware.com) , including an online book. Love them tarballs yum yum
:cool:
Editing this one more time for fun!

[ 01 November 2001: Message edited by: jaygee432 ]

[ 01 November 2001: Message edited by: jaygee432 ]

[ 01 November 2001: Message edited by: jaygee432 ]

[danrees]

I have used a wide range of Linux distributions (Slackware, RedHat, SuSE, Mandrake, Debian...), and I have found Slackware to be what I would describe as "clean". By this I meant that it has enough software to carry out almost any task, but isn't rendered unusable by a 1001 services (although I admit they can be stopped, but some newbies won't realise this).

I have also found that compilation of software on some distributions is a nightmare, particularly SuSE 7.2. On the other hand, I have never had any problems compiling software on Slackware, and I actually prefer to do this in many cases rather than installing from RPM.

The only thing that I don't like about Slackware 8.0 is it's dodgy print support. I am yet to figure out how to get an average printer working using APSFilter.

I'm mainly using RedHat 7.2 now, but Slackware is on the system at my parents house. :)

[mangeli]

Several things. One, RPM comes standard on a basic slack install. Meaning you can use rpm -Uvh to install any rpms. The problem with that is that generally RPM's are built on redhat/mandrake systems. They may not always work on slackware.

Second: it comes with a package manager. installpkg blackbox.tgz would install blackbox. This is the default slackware "package manager". Works rather well.

Thirdly, if you try ./configure on something that wants something you don't have installed, it will error out.

If you try make or make install on something that wants stuff you don't have it errors out.

In general, compiling and installing from source is cleaner and results in better programs for your box because they are built specifically for your box. You might be running something someone else is not.

I highly recommend slackware, we're using it at work as a web/email server for the past year now.

Runs great.

[X_console]

Now that you know about Slack's package manager, here's what you don't know. It's not as advanced as other package managers in that it won't do auto-upgrades for you. It doesn't check for dependencies either. For me these are fine because:

1. I like to know what's being upgraded and with what version.

2. I always check the software developer's website to see what dependencies are needed as well as what bugs are in the program.

[Strogian]

About slackware's package manager, where do you get these packages? I've never seen one.

[ 01 November 2001: Message edited by: Strogian ]

[mangeli]

www.linuxmafia.org (http://www.linuxmafia.org)