[Slackbuilds-users] new maintainers omitting READMEs

Willy Sudiarto Raharjo willysr at slackbuilds.org
Tue Mar 25 16:16:38 UTC 2025


> 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).

Did ALL those 1500+ packages landed on SBo? I'm sure it should be less 
than that. If you want to keep your README long and include all the 
details, be my guess, but keep it in your repository. Don't force your 
way of preferences into others where most people are happy with the 
current README works now.

We are talking about SBo in context right?
Why does this  include sbopkg which is NOT part of SBo project at all
It's just a third party tool that helps people to build script taken 
from SBo to native Slackware packages.
>> 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.

Well, that's true, but you don't have to include the WHOLE README right?
At least you know what this script is and besides, you can see the 
homepage URL in each of the script page. That gives you idea about where 
to find more information about the script is all about.

-- 
Willy Sudiarto Raharjo
-------------- next part --------------
A non-text attachment was scrubbed...
Name: OpenPGP_signature.asc
Type: application/pgp-signature
Size: 840 bytes
Desc: OpenPGP digital signature
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20250325/d97569c6/attachment.asc>


More information about the SlackBuilds-users mailing list