Hello All,

I am installing slackware 15 from the live iso (which I burned on a usb). In the installation, it said that it is installing the live distro, or something in those lines. I do not want the live system to be installed or to have KDE or anything else to be installed.

So would setup2hd install me a bare slackware 15.0 system? Or should I have choosen the "Install frpm HTTP/FTP server". If I would have choosen that, what address to supply, if any with that choise?

Regards

What exactly the installation said would help us, cause the pharphrase has me confused.

KDE is the default desktop. There are others to choose from available later in the install process.

If you don't want to install anything I suggest using a "LIVE" iso and to boot from that each time you want to boot Slackware.

As I understand it installing from a HTTP/FTP would mean that you need to connect to a mirror and it will download and install from that mirror ........ happy to be corrected.

By the way. Welcome to Slackware and the forum.

1 members found this post helpful.

Hello again.

Thanks for the welcome.

At first i have choosen the option that was installing the live cd system onto the harddrive. That is not what i wanted.

Then i installed the system again using the live cd iso, which i had written to a usb and booted off of it. But this time i have choosen ftp/http server for the source, and it installed the system.

Now i will be configuring the elilo.

Hello all,

Is there a package manager other than slackpkg that will install packages from slackbuild.org. I am new to slackware.

Regards

I think you need to familiarize yourself with SlackBuilds and the best place for that is their site at the link below. The HowTo and FAQ pages would be the place to start. SlackBuilds have install scripts to install the software so you don't need a package manager. I'm not really sure what your question/concern is here.

https://slackbuilds.org/

1 members found this post helpful.

slackpkg is only used to install/upgrade/manage official Slackware packages. By default it will try to remove third party packages from slackbuilds.org, so you must use slackpkg's blacklist feature to prevent it from looking at packages with the SBo tag (see /etc/slackpkg/blacklist). It can't do anything else for managing slackbuilds.org packages.

There are third party package managers that can be used to manage builds, dependencies, queues, and packages from slackbuilds.org.

I use 'sbopkg' and its included queue generating tool 'sqg', found here: https://sbopkg.org/

There are other third party package managers out there that I have not tried myself but others on the forums use:
'slpkg' - https://dslackw.gitlab.io/slpkg/ (With package build hosted here: https://slackbuilds.org/repository/15.0/system/slpkg/)
'sboui' - https://github.com/montagdude/sboui (with package build hosted here: https://slackbuilds.org/repository/15.0/system/sboui/)

There's probably others, but thats all I can think of atm.

1 members found this post helpful.

I should not have aksed another question in this thread. Sorry about this.

I have read that there is no dependency management in the package system of slackware. My concern is to screw up when installing packages.

How do you check manually for dependencies before installing a new package in slackware?

I will be reading SlackBuilds HowTo and FAQ.

Thanks.

I will be looking at the blacklist feature of slackpkg. When I install something, it should not remove what I installed from the system.

Thanks

Let me see if I can help explain this:

If you stick to software that is part of core Slackware (full installation), you have two choices to keep it up-to-date. No dependency resolution is needed.

1. Manually check for updates at slackware.com, or whatever mirror site you choose to use. Download them and install them (installpkg).
2. Use an automated tool that does this for you.

You can also obtain software via Slackbuilds. This does not provide packages ready to install. It provides links to source code, and scripts that you can use to compile that code into packages on your own computer. These can be installed on your computer using the regular package management tools (installpkg, removepkg), and your Slackware installation will know all it needs to know about them. Slackbuilds has notes on dependencies, but you need to pay attention to them, build them, and install them.

Other tools are available to automatically deal with Slackbuild downloads and dependencies.

You can also go directly to sources of other software, download the source, compile and install it following their general directions. Slackware's package management tools will not know about it, and things might break (or will break, eventually).

Ever time you rely on using an automated tool, you run the risk that a later manual step will upset the automated tool. The tools will run into "I didn't know you did that, so I broke it for you. Thank me later" mode. That is where blacklists come in. If you install Slackbuild software (manually or automatically), the automated tool that looks after your main Slackware installation needs to be told to leave those alone.

This goes triple if you install stuff without creating a Slackware package. You never know what Slackware or Slackbuild update will break it.

1 members found this post helpful.

I am new to Slackware. Wanted to try it for a long time.

I have installed Slackware 2 days ago, and I am starting to like the whole slackpkg, and SlackBuild concept. That is really nice. For instance, I did not pay attention when installing fzf today, and then realized that I have not payed attention to the dependencies. Well it is the learning process.

I wanted a daily driver that is close to UNIX. That will not have trouble with graphics/display or any other drivers. And a system that provides a good environment for developers. So Slackware it is. Hope to not change, or distro hop to another system. So far I had one problem.

Thanks.

Hi rzdndr,

The Old Tech Bloke has a video that explains how to install slackbuilds. His channel is well worth a look at if you want to learn the easiest way to use slackware. Lots of info on setting up window managers other than kde.

Easy package management with slackbuild helpers

In short as mentioned above I downloaded sbopkg from sbopkg.org and installed it with 'sudo installpkg sbopkg*'

By default it points to the slackware-15 build tree so first you have to sync with it.

sbopkg -r
You can then fire up the gui tool by running 'sbopkg' and use the search line keyword to locate what you are looking for.
All programs have a Readme which lists the dependencies.

You can exit sbopkg and use 'sqg -p <packagename>' to create a dependency queue for the program.

You then return to 'sbopkg' gui and can select to install the queue however I find it just as easy to use the command line.

sbopkg -i <packagename>

Select install from queue file and answer yes to all questions. Done.

By the way you did a good job installing from the live iso. Dependencies aren't usually a problem as long as you have all development, libraries, X programs and Xap's installed. You can install them all by running.

'sudo slackpkg install d'
'sudo slackpkg install l'
'sudo slackpkg install x'
'sudo slackpkg install xap'

And remove kde by running
'sudo slackpkg remove kde'

On the odd occasion when a program has a missing dependency try running the programs command from the terminal the program will spit out a message listing the dependency file as being not found

Copy and paste the file name to

'sudo slackpkg file-search <filename>'

it will list the package that the file belong to.

1 members found this post helpful.

Hello,

Thanks for the link to the "Old Tech Bloke" video. Helpful videos...

Will take a look at the sbopkg.org site.