[Slackbuilds-users] Suggestions for SlackBuild Usage Howto
msi at malbolge.net
Fri Aug 2 21:29:45 UTC 2019
Am 28.07.19 um 21:52 schrieb Jheengut Pritvi:
> Great initiative.
> Keep up the good work.
Thanks for the kind words.
The problem is that keeping up that good work doesn't really make any
sense if no one with write access to that page agrees to merge it. So,
I'm just gonna wait.
> On Sun, 21 Jul 2019 at 20:19, Michael Siegel <msi at malbolge.net> wrote:
>> I have some suggestions for improving the SlackBuild Usage HOWTO at
>> The first section (“Caveat”) currently reads like this:
>> All of our scripts are written and tested for usage on the latest
>> stable release of Slackware with full installation and updated with
>> latest patches; if you're trying them on older versions of Slackware,
>> you should read this page referenced in our FAQ.
>> My suggestion is to change that to:
>> All of our scripts are written and tested for usage on a full
>> installation of the latest stable release of Slackware updated with
>> the latest patches. If you're trying them on older versions of
>> Slackware, you should read this page referenced in our FAQ.
>> Then, the Howto does not mention verification of the downloaded source
>> packages. I think this should either be added to step one or be
>> step two. It could be worded like this:
>> To verify the downloaded source's integrity, first run `md5sum
>> chemtool-1.6.14.tar.gz' to get the MD5 sum of the downloaded source
>> archive. Then compare it to the MD5 sum shown in the `chemtool.info'
>> file. If they don't match, something is wrong.
>> I just realized that Step 1 already doesn't mention verifying the
>> SlackBuild's GPG signature. I think that should be included in the Howto
>> as well.
>> So, maybe, it would be best to split Step 1 up like this:
>> * Step 1 – Download and verify the SlackBuild archive
>> * Step 2 – Download and verify the application's source archive
>> What do you think?
More information about the SlackBuilds-users