[Slackbuilds-users] Discrepancy between SLACKBUILDS.TXT MD5SUMs and .info file MD5SUMs in a couple slackbuilds.

Bob Funk bobfunk11 at gmail.com
Tue Aug 6 09:10:47 UTC 2024


Really the only problem is how the SLACKBUILDS.TXT presents the md5sums for
those cases, which is inconsistent with the rest of the md5sums in
SLACKBUILDS.TXT.

I was trying to leverage SLACKBUILDS.TXT with some parsing scripts and
expected to find whitespace there. I could use the info files instead to
get the correct md5sum info, I just wanted to raise the issue to the sbo
list in case there was something better that could be done.

It's not really the way the .info files are formatted, as you point out
with where the whitespace is on the next line. I guess it's more about
something wrong with how that SLACKBUILDS.TXT is parsing the info files to
generate those entries. Maybe that's a better place to fix it, so
additional requirements about md5sum formatting in info files aren't needed.

On Tue, Aug 6, 2024, 03:13 B. Watson <urchlay at slackware.uk> wrote:

>
>
> On Tue, 6 Aug 2024, Bob Funk wrote:
>
> > Perhaps enforcing spaces before backslash/escape characters in .info
> files should be done so the files are consistent? Could even be added to
> sbolint I suppose.
> > I'm not sure what is generating that SLACKBUILDS.TXT but perhaps its
> parsing code could also be adjusted to allow for those cases as an
> alternate fix.
>
> sbolint doesn't check for this... it does check that there are spaces
> between multiple md5sums, but in the case of vst3sdk, there *are*
> spaces, they're just on the next line (indentation on the line after
> the \).
>
> I could add an explicit check, wouldn't be much trouble. Looks like we
> have 4 builds in the repo with this problem:
>
> academic/gephi
> development/openjdk8
> haskell/haskell-test-framework
> libraries/vst3sdk
>
> Another check that should maybe be added: do we want to *require*
> indendation on continuation lines? Example:
>
> DOWNLOAD="http://whatever.com/blah.tgz \
> http://other.com/foo.tgz"
>
> The 2nd line ought to be indented. Same thing could happen with
> md5sums... right now, these don't get checked for, and really they
> don't cause any problems for tools like sbopkg or sboinstall. So how
> picky should we be about whitespace?
> _______________________________________________
> SlackBuilds-users mailing list
> SlackBuilds-users at slackbuilds.org
> https://lists.slackbuilds.org/mailman/listinfo/slackbuilds-users
> Archives - https://lists.slackbuilds.org/pipermail/slackbuilds-users/
> FAQ - https://slackbuilds.org/faq/
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.slackbuilds.org/pipermail/slackbuilds-users/attachments/20240806/bad0ede2/attachment.htm>


More information about the SlackBuilds-users mailing list