Same here.

I'm curious, with repos you mean third-party repositories? Different repos have different software packages, that's true. What do you mean with « installer/different installing »? A package manager? You can use as many package managers as you like, most are using pkgtools' installpkg/upgradepkg to do the installing of packages (except for spkg, I think), and packages are recorded in /var/log/packages as well as /var/log/removed_{packages,scripts}, so if you install a package with, say, slackpkg, and another one with slpkg, both will show up in /var/log/packages. There is not much a package could know about each other, some third-party repositories like slacky.eu have dependency information, but other than that, there is little information a Slackware package carries. Or maybe I misunderstood you.

Thanks @ enorbet for letting me know that the nvidia installer works well for you. It seems AlienBob and the slackbuilds script are pulling the same version (346.59). If I check nvidia's website it seems they are up to 346.72 in their long lived branch. When I was on debian sid I would use smxi to pull in the latest kernel and nvidia drivers. Never saw a difference in performance. But I will think about using a newer version.

Learning will ensure success.

I corrected for you, maybe because I see daily (in Real Life ) hundred examples of guys who read carefully (but with no demonstrated interest), and they still are at glorious level of ZERO point ONE, after several years of study...

1 members found this post helpful.

Reading implies understanding. If you don't understand you're not really reading. I can read the words in a foreign language, but, if I don't speak the language I won't understand anything. I suppose I should have written read, and understand the documentation.

Well, I don't remember which package it was, but sbopkg didn't know about it, and neither did slackpkg. I had to upgrade with upgradepkg.

At the moment:
but


So I guess the policy is: if you install a package with sbopkg, you remove/upgrade that package with sbopkg. If you install a package with pkgtool, you upgrade/remove that package with pkgtool, and so on.

Yes, but I too have encountered many people that read the documentation and get thigs to work. Then next week the same problem and again searching the documents. The read doesn't stick.

This won't work, upgradepkg expects a file. See /sbin/upgradepkg, it's just a shell script. Use something like slackpkg to upgrade the base system -- or upgrade it by hand using pkgtool/upgradepkg if you have the binary package ready.

sbopkg is used to upgrade/install SlackBuilds from SlackBuilds.org. It will start the compilation of a SlackBuild and install the resulting binary package via upgradepkg. pkgtools/upgradepkg expect a path to a real existing binary package. You can also build SlackBuilds manually and install the resulting binary package (saved in /tmp by default) using pkgtool/upgradepkg.

sbopkg does not know about packages from Slackware's "series", and slackpkg does not know about SlackBuilds from SlackBuilds.org (though you can remove SBo packages using slackpkg).

removepkg will remove any package that has been installed with any tool. And in the case of removepkg, you can use the package's base name (like "removepkg cups") instead of giving the full package name.

2 members found this post helpful.

Funny, I didn't realize until now that installpkg and friends are totally local. They are not aware of any repos. You have to download the package "source" first. I assume upgradepkg -install-new is pretty much the same as installpkg with a new package. Upgradepkg just knows how to "overwrite" existing package stuff.

With the package "source" I mean the txz-file as opposed to the package in /var/log/packages.

Well, that still confirms what I said, except for the 'removepkg'. I guess it removes any package in the /var/log/packages.

You install with sbopkg, you manage with sbopkg. You install with pkgtool, you manage with pkgtool. You install with slackpkg, you manage with slackpkg. That's partly due to the repo where the package is found, but also due to the local txz-file location.

You probably CAN cross-use them, but that'd be making things difficult.

The OP seems to have disappeared. I think we frightened him.

upgradepkg is pretty versatile. As you surmised, --install-new will essentially allow an app to be installed if it isn't already. That's why many script or command lines will include upgradepkg --install-new --reinstall *.t?z, because this will upgrade any old packages, reinstall packages that don't have different versions, and install new packages that weren't already present on the system.

And with those various tools you mentioned, you can use pkgtool to "manage" all of them, since all install packages that conform to standards pkgtool uses. But, as you mentioned, the stock Slackware tools (minus slackpkg) are all local only, so pkgtool will only be able to "manage" the programs by viewing the contents and removing the packages.

That happens sometimes when people are told there is stuff to learn...

Hi,

Sad but true! Some want spoon feeding & hold their hand to do anything.

Well looks like he is running Arch now... so long and thanks for all the fish... he should change his nick to IwannaRetch.

Gone are the days where learning was a requirement to use Linux. Seems like all these new trendy distributions, and even some of the older established distributions (Debian, what happened to you), want to provide a Desktop experience that requires no knowledge of the Operating System. To a certain extent this is good, but it has gotten out of hand IMHO. When I first started using Linux (this is what enticed me to migrate from Windows), the more you knew, the more empowered you became by your Operating System.

I registered on this forum again after having lost my account credentials that I used to use in the early 2000's. I joined this forum originally back in ~2002 because of the wealth of information available regarding Linux topics, not to be spoon fed information. The reason I registered was so I could partake in the Slackware forums.

Since coming back to LQ, I've noticed that when you browse the rest of LQ (most, not all), it seems like every other post is someone asking to be told exactly what command or exactly what to do to accomplish whatever remedial task(s) they can come up with. No one wants to read documentation or attempt to at least try to figure out their own solution. Tell them they need to use the command line or that they won't have a GUI until they edit a few text files etc, and they jump distributions. Worse, they go back to Windows.

3 members found this post helpful.