Should READMEs on SBo be more descriptive? Probably. But some developers don't provide a concise description of their programs [...]They all do for first line in sbopkg menu.
sbopkg is designed to help you build the source into native Slackware packages, not to help you READ the DETAIL of the script.
I'd guess that's mostly nonsense; many people find most their programs in software managers including programs to run build scripts, such as sbopkg: I do this weekly. Most what I installed I found in sbopkg, not by finding a webpage for software I don't even know exists, which only happened in rare cases. For third-party repositories (such as slackers.it and quasi-official alienBOB & RLWorkman's ones (them being Slackware team members)) it's even more the case that I look in repositories to find/know what I want to try. Dependencies need READMEs just as much as what they depend on, because people may read all lines in sbopkg (I did originally and maybe once/year, and all updates, or at least searching through for 'added') and it's common to add software depending on those, or even just write a program depending on them; a large number of dependencies have software using them by multiple maintainers, and I occasionally install libraries/APIs I want to try, and made a SlackBuild of a library (though it has test software).
Again, we are talking about 2 different thingsSBo is the repository that contains all the READMEs, while sbopkg is just a third party tool outside of SBo.
Just browse the SBo website for information and use sbopkg (or any other third party tool) to build it. That should solve your problem.
-- Willy Sudiarto Raharjo
OpenPGP_signature.asc
Description: OpenPGP digital signature
_______________________________________________ SlackBuilds-users mailing list [email protected] https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/ FAQ - https://slackbuilds.org/faq/
