How to handle lack of dependencies and dependency resolution in Slackware?

[Tinku-Jia]

right now I am using Ubuntu and wanted to use slackware. But I am not able to do the same because of dependency resolution. Well the slackware is kind of the distribution which believes dependencies are the work of users. How all the slaware users will tackle the above mentioned problem?

[Aniela]

All the users who are using Slackware from the long time are aware of the fact that it did not supposed to resolve all the dependencies by default. However you can utilize various kind of the utilities like slapt-get in order to resolve the dependencies issue.

[Jezriah]

If you have done the full installation of the Slackware then you will not require to worry about the dependencies. It makes the installation quite easy as dependency tracking is lacking in the software. Rest of available distros you will require to manually write all the dependencies list. However you have to take care of the thing that package manager is not deleting all the dependencies. You will not require to do the same with Slackware.

[aSITA]

Ubuntu and Slackware has been developed for the totally couple of different kind of the users. Once you have installed Ubuntu on the system it will give you lots of options. If you are not aware of what are the packages then it would be more useful to have a system which is having ability to handle all the routine system management.
The Slackware seems to be classic distribution. It has been developed when all the softwares were distributed into binary or source form and compressing the same. the word tar means that it’s a tape archive and it has become primary archiving mechanism.

[Evoldo]

There are multiple package management tools provided in the Slackware and some of them are using as a primary package management. Slackware users are supposed to download source code in tar.gz or .tgz format and after downloading that they are unpackaged it.