using the slackbuilds on current
by slackmensch from LinuxQuestions.org on (#5H97F)
I'm trying out slackbuilds on current and I'm wondering how things are meant to work.
I've cloned Ponce's github repo of slackbuilds (Is this the right place?) and I've built a few emulators and games but the process seems kind of cumbersome:
Are there prebuilt packages somewhere official-ish for all these slackbuilds, at least the ones that compile on current? Have I missed a script to automate this process? Why put the package in /tmp instead of the more obvious directory containing the Slackbuild script?
I almost went down the rabbithole of trying to suss out all of vlc's dependencies when searching revealed someone had already built and uploaded the package.


I've cloned Ponce's github repo of slackbuilds (Is this the right place?) and I've built a few emulators and games but the process seems kind of cumbersome:
- read whateverslackbuild.info and wget the source code url
- chmod +x whatever.Slackbuild
- ./whatever.Slackbuild
- installpkg /tmp/whatever-blabblah.tgz
Are there prebuilt packages somewhere official-ish for all these slackbuilds, at least the ones that compile on current? Have I missed a script to automate this process? Why put the package in /tmp instead of the more obvious directory containing the Slackbuild script?
I almost went down the rabbithole of trying to suss out all of vlc's dependencies when searching revealed someone had already built and uploaded the package.