I came across this site:

Are there any precautions while using packages from this site? I tried to search linuxquestions.org but could not find any reference to this site.

I've never heard of the site (and it is blocked at my work), but it is usually more desireable to use a SlackBuild and compile the software for your computer with your dependencies. Have a look at http://slackbuilds.org with a tool like sbopkg.

About the only time I make an exception to using SlackBuilds is when I get something from Eric Hameleers (aka alien bob), since he is a primary developer with Slackware (his packages and slackbuilds are available on www.slackware.com/~alien/slackbuilds/, but I do know a few make exceptions for kikinovac's MLED repository and a few others.

EDIT: As far as precautions go, make sure that you are getting any needed dependencies, since Slackware does not do dependency tracking. Also, once using a software repository, it is best to stick with only that one, so you don't start getting mismatched binaries (siteA packages may be expecting a certain version of a lib that is a dependency, but siteB is shipping a different version that you installed for a different package)

First time I have seen that site.
Anything 'official' is A++
Anything 'armedslack' is for ARM architecture
Anything 'universe' from Alien or rlworkman.net is A++ (Slackware developers)
Anything 'slackbuild' from slackbuilds.org, jgeboski, willysr is A++
The rest are probably only A+

This also appears to be a similar one:

Slackware is getting popular!

Those two have existed for ages. You were all asleep.

Or you're getting old... Or both...

I wasn't asleep, I just didn't care to look

Including me. To help Slackers discover all such resources in less than ten years a single page in SlackDocs gathering them would help. It could include categories like third party repositories, tools (sbopkg, sbotools, slapt-get, sbbdep, spi, slpkg, spkg, depfinder...). These resources are all somehow "unofficial" so maybe it would go against SlackDocs policy to list them? But then all needed warnings and caveats could be included.

I also realize that some of these resources are listed in Onebuck's Slackware-Links but not so easy to find there.

I think that this page could be mentioned in the home page under "Getting Started with Slackware" and am ready to contribute (some editor should create the page first, then).

By the way I still think that this other page could fit there also and in the Slackware namespace as it is actually not an how-to.

The page "get_acquainted_with_slackware" could easily be transfered to the "slackware" namespace but since that namespace is only writable by the site's admins and editor team, you would lose control over your page's content once it is moved.
Similarly, what would you like to write in a new page under "Getting Started with Slackware"? Note that only the HOWTOS section is open to contributions, the other main namespaces are read-only except for the editors/admins.

2 members found this post helpful.

I retract this request and this suggestion. Thanks for the clarification and the reminder, and I apologize to all for the noise.

I have never used that site before but after a quick look around it seems like it mostly is just a search engine / database for packages. It does not appear the site operator is hosting much or any of the content. To that end it seems like it might be a nice tool, to see if there are binaries for something in any of the major community repos.

I would say for safety's sake though you should pay careful attention to where those links are pointing and where anything you chose to download is coming from. Certainly anything that points back to the official mirrors is probably okay. Sites operated by people like Alien Bob that have been long active in the community are certainly trust worthy as well.

Here are the usual cautions:
1) Packages are installed as root doinst.sh runs as root. Even if 'you' never run the software you install that script could do literally anything
2) Binaries can be backdoored and how would you know (of course source could be too)
3) A badly built Slackware package can easily mess up your file permissions or overwrite critical configs, etc

I'd say its a nice tool someone took the time to make, and if you want to use it go for it. Just make sure you know where any package you install is ultimately coming from. The same can of course be said from any build script anyone gives you. In summary think about the origins before you run code you have not personally audited.

I once had found a github hosting a lot of slackbuild scripts. Some of the scripts were for things you could not find anywhere else. It only had the scripts and nothing else. You had to find the packages to go with the script yourself. I always check the scripts out first regardless of the source. I believe this was the one:

https://github.com/PhantomX/slackbuilds

Here's is another one:

https://github.com/Ponce/slackbuilds

This one looks like a mirror of SlackBuilds.

It isn't a strict mirror of Slackbuilds, which only targets official releases. The repository from Ponce is the one people should use when they are running current as is pretty clearly stated at the top. Essentially think of it as a development branch to get ready for the next Slackware release.