In normal cycle (when new stable is released), we normally do not update the whole repo by ourself and we need maintainer to pro actively submit updates via submission forms.

During development cycles like nowadays, some packages are broken due to updates in current so we need to fix things to make sure they are fixed when new stable is released. Some maintainer prefer to wait until next stable

Thanks for the reminder. PPA maintainers have same advice for Ubuntu fans.

Sorry sir. I don't have enough time to bug track and read various websites and mails for every single package which I install from SBO. Therefore, if SBO maintainers let everyone threats security of Slackware users by bad slackbuilds or buggy codes, I prefer to change my habit and use Eric and Roby repositories as main source of third party packages.

Then you may need a package not provided by Eric and Robby. Will you compile it by hand or write your own SlackBuild? In such case you will also have to bug track packages and read various websites and mails for every single package you install.

In general I find SBo to be pretty good with updates. But the point was that slackbuilds are maintained by volunteers, so it is true that they are sometimes abandoned, but in my experience that's for the rarer pieces of software. Just to name a few that I like--TeX Live, Libreoffice, R, Audacity, Clementine, Digikam, Duplicity, Lame, Nvidia drivers, Recoll, Transmission, Yakuake--all on SBo, all brilliant But, at least you have the freedom to choose

I appreciate the people that maintain SBo, and the people that maintain the SlackBuilds themselves. It is a valuable resource that people can share their builds and the rest can benefit from. Sometimes maintainers fall behind, or lose interest in a project which is sad but hopefully there is someone that can pick up the "Slack". I have found a few packages on there that are updated past what Alien has in his repo, So it happens to them all. (Appreciate you too Eric, I don't know what I would do if I had to compile something like LibreOffice or Plasma 5).

PS: Pale Moon is broken on -current and has been since Feburary.

1 members found this post helpful.

Travis, then perhaps Slackware is not the distro for you. With Slackware, there is PV, Eric, the team, SBO, and various tools to help, but ultimately you are the admin. If you think SBO has unmaintained packages then pick up the slack and help maintain some. Don't even get me started about the number of unmaintained or poorly maintained packages on other distros....Not naming names but 25K packages with 1k packagers is 25 per person...just saying, many of those are poorly maintained.

1 members found this post helpful.

It builds ok here (most recently on 29th March). I've just installed it, and it works well enough to log into LQ, and I'm posting this reply with it right now.

Apparently it still has the same lousy textbox bug that Firefox cured years ago. meh

libwebp, slackbuild is for 0.4.3 but works with 0.5.0

webkitgtk, slackbuild is for 2.4.9 and seems to be working for 2.4.10 *

gnucash, slackbuild is for 2.6.6 but works with 2.6.11

If it's out of date you update it. What's the problem?

* I'll know for sure for sure in about 20hrs time... it really is a slow build.

official endorsement is official

Seriously? I can do a full fresh install and build Pale Moon 25.8.1 or 26.1.1 and each one gives me a seg fault. Maybe I need to refresh my mirror.

Thanks for the feedback.

Webkitgtk has been updated last month in master branch

Gnucash updated to 2.6.11 as well.

People should look in master branch in GIT repository instead in the Web since 14.2 is not out yet

1 members found this post helpful.

Thank you I will have a look.

But my point was that Slackbuilds don't just work for the version stated but that they often work for updated versions as well.

So arguments that slackbuilds are for out of date software might be weaker than the proponent thinks.

As long as upstream doesn't make major changes, the script should work on newer version.

I wonder why you try to have a finger in every pipe. I didn't talk about unmaintained or poorly maintained packages. Next time read the post before quoting it.