I have decided to check out Slackware, mainly because of the direction Ubuntu and similar distros have taken, too user-friendly. I want to have control of what I am doing. So I thought I would check out slax.

The first thing I've learned is that pkgtool does not check dependencies. That is something I'm definitely not used to, but I am willing to learn.

My main question is this. How am I to learn what packages depend on? I like having a lean, minimal system and would like built my system from the ground up. What would be the best way to learn this?

Thanks.

Best start at Slackbuilds.org where the dependencies are clearly pointed out and usually available from the same site.

That seems like a good site, but I am looking for dependencies for the official packages. For example, I am wanting to know exactly what packages I would need to install in order to install Gnome. I installed just a minimal slack system, now I want to add certain packages.

Any suggestions?

Well, many slackbuilds from SBo graduate to become part of Slackware itself so I guess it depends what you mean by 'official' . To install gnome, which I admit I have not done due to being quite happy with xfce, I believe this site is worth a look:

http://gnomeslackbuild.org/

but I am sure others who have used gnome under slackware can give a better steer, I do not see 13.37 mentioned there....

Now that you mention XFCE, I think I will use that, at least initially until I get a good feel for slack.

Say I install the "A" and "N" package sets, where would I go to learn exactly what packages X would need? Same for XFCE?

You would be best to do a full installation of Slackware and then select xfce using xwmconfig. I do this on my own system and simply exclude the kde set (and emacs!) during installation although perhaps as a slackware starter you would be best to install this as well. Full installation of Slackware is not so big these days when HDDs are all so big.

I would do that, but I am installing in a virtual machine that I need to keep small. I may try the full installation on a different computer that has more space. Would doing a tagfile custom installation be good for what I am wanting?

As an alternative (or possibly a stepping stone to Slackware) you could install Salix: http://www.salixos.org/wiki/index.php/Home
Salix is based on Slackware, but uses the slapt-get package manager that does resolve dependencies.
All Slackware packages are fully compatible with Salix, and vice-versa.
Since Slackware 13.37 was just released, Salix 13.37 should be out very soon.
I have been using both Slackware and Salix since Salix first got started. I can verify that Salix is excellent; and just as reliable as Slackware.

Salix, a distribution based on Slackware, uses additional *.dep files to handle dependencies. While running slackware, you can easily check if a certain program you are about to install is also on the Salix repositories.

For example, if you wanted to install xfburn, you would find the *.dep file here. Which is simply a list of other packages needed as dependencies (seperated by commas).

By the way, all of Salix' packages are fully compatible with the official Slackware distribution aswell.

As other people pointed out, slackbuilds.org lists the important dependencies on the page with the link to the slackbuild/sources.

The most traditional way to check for needed dependencies, is to simply extract a source tarball, and run the `configure` script (if any) which will check if everything is in place. Obviously if it produces an error about "failure to find ______" then you need to install _______ as a dependency. Before you can succesfully compile it.

Hope that helps.

For my opinion the best learning source is linuxfromscratch.org and i think that every linux distro are built starting from there (maybe also Slackware/Slackware64).
Another place could be www.gentoo.org when explain in documentation the stage1/stage2/stage3 difference.
Dependency tracking and managing is very big trouble in every linux distro.

In Slackware an old method is discover the libraries that an executable uses by typing:

ldd <executable name>

then checking result and content of file slackware/MANIFEST.bz2 in install CD/DVD to find
relating packages.

In my little experience installing packages in a, ap, l and n group is sufficient for an
minimal system with terminal only and no X.

look every official sbopkg source build has a info and read me every Slackware build has that. So read them for all the dependencies . This is why we spend many hours creating a read me and info file. hope this helps.

some one asked me why I understood. I told them I read everything.
Thank you Pat 13.37 solid

Maybe this will help?
http://www.stabellini.net/depslack.html

I use this: tracepkg

Try this. I experimented with Absolute which is same Slackware under-the-hood and worked nice. Only one command in terminal for quick install and done but you will need patience if slow network.
http://gnomeslackbuild.org/download/

Hi,

Your assumptions are wrong when it comes to Slackware. PV has been doing development/maintainer from the beginning for Slackware, long before LFS. Maybe certain Gnu/Linux maintainers started out with a LFS model but most serious maintainers won't.

Yes, for most hold your had distributions! Most experienced Slackware users will use available tools to setup a system. Loads of experienced users will rely on SlackBuilds.

Yes, yet again most work has been done at SlackBuilds. Unique apps can be setup for Slackware with a little more effort.

I like;
Minimal System is SlackWiki method as to what packages you should install to have a base system.

HOWTO make your own custom Slackware install disk is Samac's LQ technique, some cautions but good. 'Here is a method of cutting your Slackware to fit you by using Alien_Bob's mirror-slackware-current.sh script.'

mini ISO image is a 'CDROM to boot, and install packages from an NFS server or local hard disk'

The above links and others can be found at 'Slackware-Links'. More than just Slackware® links!

1 members found this post helpful.