[Slackbuilds-users] new maintainers omitting READMEs

[David Chmelik]

On 3/24/25 1:22 AM, Willy Sudiarto Raharjo wrote:
>> I doubt it; no one wants to 'go upstream' for thousands packages: 
>> just have sufficient READMEs, which historically normally had 
>> everything except Internet site.
>
> I doubt people would read EVERY README for thousand packages
> they just need to see some packages they need and README is just enough
Speak for yourself: I built 1,500+ SBo packages, and a few other people 
use almost as many or maybe more.  README is enough when it's more than 
terse one-liner--following template--historically using entirety of 
upstream README.* except URL.  One-liner is for sbopkg menu, not 
substituting for README, which is just sloppy/lazy/unprofessional, 
including some use jargon so one must hunt down README to find out what 
the software even is (let alone if one wants/needs it)... maintainers 
could take a minute or two to copy that in instead of wasting minutes of 
thousands people forever (often finding the software isn't something 
they want/need).

> at least they know what this script is all about
Not at all; not descriptive enough, including some use jargon.

> if they need more information on how to use, they should follow 
> upstream documentation for more detailed information
Upstream README.* should be README, because it's more information on 
what a piece of software even is.