the scripts that you can find on the official SlackBuilds.org (SBo from now on) repository are available for the latest Slackware stable so, in many cases, they won't build on current as they are provided.
if you need a repository that has patches to build them on current, please use this project (not supported or endorsed by SBo)

https://github.com/Ponce/slackbuilds

if you want to see the list of the patched scripts, there's also an alternative interface available at

http://cgit.ponce.cc/slackbuilds/refs/heads

this started years ago forking the SBo's repository as a personal effort to have a working queue available for the scripts Matteo used for his boxes but David's contributions made it something that aims to be a more complete aid to SBo users that use current on their machines: just don't expect that everything on SBo will be patched to work on Slackware's development platform as we don't want to do the job of every script maintainer and this project is a best-effort thing.

SBo supports building its own scripts on clean slackware full installation: we would go crazy trying to support any setup out there that we have not tested ourself for everyone of our 5000+ scripts.
this policy applies also on this humble, unofficial, attempt to let SBo things build on current.
following this it should be obvious that issues related to custom installs shouldn't belong in this thread: please open another one to discuss such things, also if you are not sure if the error you got is related but you are aware that your setup is a non-standard one.
describe your problem here only if you are absolutely sure that it has nothing to do with your custom setup.
there's nothing to be added in our repository for the benefit of other slackers if someone is missing dependencies from a slackware full installation or has stuff installed in /usr/local or has installed other third party non-SBo stuff that might be incompatible and so on.
there's no need to say it but if someone else don't agree with this policy and wants to support also non-standard setups is free to do it (but in another topic ).

so, what is this thread for?
risking to be repetitive, report issues here only if you have already tried the scripts from our repository and they won't build on a clean and full installation of Slackware current.

also, if you want to report a problem that applies also to Slackware stable this is not the right place, this topic is current-specific.
if you think a script on SBo shows issues (broken download, not building, etc.) on such platform write to the maintainer and wait some days for an answer (a week should be fine): if the maintainer isn't responsive after this time please post the same thing by mail to the slackbuilds-users mailing list putting the maintainer in cc

http://lists.slackbuilds.org/mailman...ckbuilds-users

if you wonder how long someone does have to not maintain a package before it will be considered abandoned, the answer is that there's no fixed time: a package can remain at a certain version for many reason (compatibility, stability, lack of updates upstream, etc.) so the lack of an actual maintainer cannot be tied on how often it gets updated.
usually the package is considered maintained as long as the maintainer is responsive and supports his script so, maintainers, make sure the email address listed in .info file is valid and stays active.
for any other question regarding specifically SBo and not this fork refer to its faq

http://slackbuilds.org/faq/

Maintainers: if we have modified your script, our suggestions are not official! We hope that our suggestions will be useful when you do your official scripts for the next version of Slackware, or we will be very happy to accept your changes now

David and Matteo

P.S. Our repository is directly usable with slackrepo and sbopkg, see

http://idlemoor.github.io/slackrepo/
https://github.com/Ponce/slackbuilds...ry-with-sbopkg

if all you want is a local copy just clone it with git

For what it's worth, many of the updates to SBo when a new Slackware release is pending will come from this repo. :-)

7 members found this post helpful.

I'd like to add that sbotools will soon(TM) get a new release which will be able to use your git repository as well.
There is a RC3 of it available as source tarball or as a slackware package.

You would enable ponce's git repo by doing
and then a sbosnap fetch or sbosnap update as appropriate.

If you have any problems with sbotools, please don't hesitate to open an issue.

Do note that this version is still just a release candidate, which makes it little more than a beta. It may of course contain a few bugs, though I haven't been able to find any so far.

5 members found this post helpful.

note that, IMHO, the most practical way to sync, as the default branch of the repository is rebased always on the latest master from SBo's git, maybe is to delete the repository and then clone it again.

the alternative is using some git-fu.

4 members found this post helpful.

You sir just made my Christmas that much better.

Having a -Current friendly repo for sbotools is appreciated beyond measure. Many thanks to you and ponce both.

So far, I've built most of the stuff on -current, relying heavily on ponce's branch (thanks, Matteo!). Only VLC is making trouble. I tried building 2.1.6 and 2.2.1, but without success. Since this isn't exactly high priority for me (I'm mostly running Slackware stable), I guess I'll wait until one of the more hardcore geeks has figured out how to build this beast.

Cheers,

Niki

I think this round you should thank mainly David: he owns most of the patches there!

3 members found this post helpful.

"owns" the patches???? They're all just suggestions, waiting for someone else to test them ... or for the next big update to break them again

3 members found this post helpful.

As I compile my VLC 2.2.1 package successfully on slackware-current I guess it is just a matter of applying the right patches. But without any backup in the form of compilation errors, I can not tell you what needs patching.

2 members found this post helpful.

Thanks, Eric. I didn't think about your vlc.SlackBuild, since I didn't know it also worked on -current. I'll take a look at this, and if I don't succeed, I'll come back with a detailed error report. Will probably be in early January.

Cheers,

Niki

I do no Ponce does a great job the whole bunch do should throw a donation jar up there. That said freshplayer I have no clue why the dependencies are such. I do understand ffmpeg but it needs to be updated that version is broken with the latest pepper. That's a drop in the bucket
So much cool stuff in there.

freshplayer from there works fine here.

EDIT: I just checked and it seems freshplayerplugin had a new release yesterday: I'll have a look and if it's ok I'll update it in the repository.

FreshPlayer has quite a few dependencies, even from my testing of it. Ffmpeg, libconfig, ragel to name a few with pulseaudio as well as optional. Ffmpeg however is the biggest headache of the built though. Make sure you have a good deal supported by it though.

Just be advised that if you update any dependency of freshplayer it has to be rebuilt all over again or it won't work.

Re: vlc, it looks like all we need to do is mix and match Christoph's SBo vlc patches: http://slackbuilds.org/cgit/slackbui...multimedia/vlc

It builds, maybe it even works?
https://github.com/Ponce/slackbuilds...multimedia/vlc

Hello Ponce,

I notice that in dolphin-emu i have to keep setting the controller device every time i
run it otherwise the controller does not work.