Okay, so I''ve been thinking lately... In recent weeks, I''ve messed around with all kinds of distros, and I''ve come, once again, to the realization that Slackware is my favorite in terms of how it has everything setup. But with my many attempts at using Debian, I have also come to love apt-get. So, I''m considering possibly starting up a project aimed to create a package managment tool for Slackware that will make installing new packages as simple as apt-get is, using the current Slackpack format. If I were to do this, would anyone actually be interested in it? Also, should I call it apt-slack, slack-get, or something completely unrelated to that?

Most people who use Slackware would rather install software themselves... I would, at least.

I use Mandrake 9.0 because of it's configuration tools (no-fuss ICS and firewall, specifically), but I never install programs with RPMs because I know how to do it myself via tarballs, and I like it that way.

[edited by - DyDx on December 21, 2002 12:05:01 PM]

See, I disagree. I think most people who use Slackware prefer it because of the way that it doesn''t do automatic configuration for you for everything. Sure, there are plenty of little tools that will (e.g., netconfig) if you so choose, but it doesn''t force you to use any of them.

As for software, generally you do have to build lots of things from source under the current system. This really wouldn''t be that big a deal, except for the fact that sometimes this requires downloading lots and lots of other dependencies, which you aren''t aware of until after you try to compile the thing.

Basically, this project would not be something that I ever really envision becoming an integral part of Slackware. Instead, I envision it as an alternative program that would help make the maintenence and upgrading of a Slackware system a bit easier, especially for those who do not wish to have to compile everything by hand.