I recall hearing of this site before. I was reminded of another terrible site whose name escapes me right now that no longer exist that carried Slackware packages. This is a bit different. It looks to be a mirror site. I personally would never get a package from this site. Why use this site when you can get your packages from the original source and official mirrors. If your looking for Slackware packages use this site instead: http://www.slakfinder.org/

1 members found this post helpful.

I'm normal user that uses a lot of programms: Blender, Gimp, Inksape, Texstudio ecc..

Normal users are the category hurt the most by the libraries version madness that originates using random packages downloaded from pkgs.org.

Lets try saying it with metaphor: if you're about placing your balls on an anvil and start hammering I can warn you that most probably it will hurt a lot, but in the end the balls are yours.

2 members found this post helpful.

On occasion I visit this site to know which distributions provide a package for a software not available through SBo or a Slackware contributor's repository that I consider building, never to get a package. But in such cases I usually first look for a Debian and Arch packaging that I could take inspiration from.

1 members found this post helpful.

On pkgs.org I see Alienbob package

Packages smashed on anvils; I find this intriguing. Do you have a newsletter?

cheers,

I don't think these are really can be compared. Essentially you don't need a script at all. Only to keep history of changes compared to default Slackware installation. Any system will do. The simplest is of course to keep things added under /usr/local + information about build option. So you can re-compile. So scripts are about how to create package. So do I need package management? If someone is building for others - definitely yes. If you don't care much sharing with others - there is no need to take care about any package management beyond Slackware offers. But people are tend to be lazy. If something is difficult to build they go for sbo-script - those ambitious - or just for binary - less ambitious. So both sbo and pkgs have place. Oh yea I just build today Apache server, oh yeah I just build today qt5 - it is good for you. You have proven yourself. Now time has come to build all Slackware from source.

I'm feeling lazy right now so I'll boot to Windows to play Diabotical

Use my SlackBuilds:

1. gnome-desktop
2. lutris

linuxpackages.net? That was an important resource back in the day.

That's the one. I used it, yes it was. Unfortunately that site went downhill really fast as a poor quality and untrustworthy site for Slackware packages. It least that's the way I saw it. I was glad to see it go.

This pkgs.org on the other hand is a lot different. Unlike linuxpackages,net, these packages are not user submissions but packages mirrored from official sources. For example Slackware-current is mirrored from slackware.cs.utah.edu. Alien Bob's packages are mirrored from slackware.uk

I am rethinking my opinion regarding this site. It can be useful as Didier Spaier mentioned.

To my surprise I just now noticed that I have bookmarked this site... on June 20, 2012!

Most of my third party packages I build myself anyway. Not counting ktown and multilib, the only packages on my system I have not built come from Alien Bob (19 of them). Used to be a lot more until I learn the art of SlackBuilds.

Doesn't pkgs.org choose the nearest mirror? That is, -current won't be mirrored from the University of Utah if there's a closer source? At any rate, Slackware packages using an official mirror like slackware.cs.utah.edu would be just as easily accessible from the Slackware web site or certain package managers, so I'm not sure it's particularly useful.

The site indexes all known repos for that distro and will show you them if you search for a package. The problem arises when you start mixing packages from those various repos as they may be built against different versions of libraries. Since Slackware doesn't include any dependency resolution, you have no way of knowing whether or not packages from different repos will work together.

If one repo built against qt-5.9.x and another built against qt-5.12.x, it might cause breakage of one or the other package depending on what qt5 version is installed on the machine.

Most people trust Alienbob's repo and it usually doesn't cause breakage with packages in SBo, but there's still a possibility of it. Many people will use his version of qt5 because of the astronomical amount of time it takes to compile it. Others like his LibreOffice and VLC packages.

I prefer Slackbuilds over any binary packages. I've had too many issues on other distros mixing official binaries, third party binaries, and self compiled software and I'd like to not repeat that on Slackware. That said, I do use AlienBob's binaries for a couple of things which are complicated to build and/or have an ocean of build time dependencies but very few or no run time dependencies outside of Slackware's full install. Chromium, for example. I use sbopkg and slackpkg+ to manage things, plus a text file for notes on less straightforward builds and to keep track of dependencies.

I feel that while installing binaries is a simpler action than building packages from scripts or by hand, using too many binaries from too many sources damages the simplicity of the over all system and increases the risk of packages and their dependencies becoming out of step with each other. I'll take a little more time/work if it means fewer potential problems, and what problems do occur are easier to diagnose and solve.

1 members found this post helpful.

What about rpm2tgz?

I personally don't trust rpm2tgz. I've seen issues on the forum where it's jacked up permissions of the system, because the rpm had weird permissions and rpm2tgz (or maybe it was deb2tgz) didn't sanitize them.

Personally, I'd much rather extract the contents of the rpms and debs and then manually create a Slackware package. I've submitted a few SlackBuilds to SBo that do this for debs (filebot and discord for sure, maybe others).