I just refreshed my SLACKBUILDS.TXT copy to test it out and everything's
good now. Thanks for looking into it.
@ willy: With the SLACKBUILDS.TXT file getting fixed by B. Watson, the
commits you added are technically no longer needed. The commits are
harmless though, so do what you want with it.
T
I was going to take dav1d but Jeremy spoke first (it's been added to
-current anyway), but I will take nv-codec-headers (also added to -current
but I'll take it until it goes 15.1 stable).
On Mon, Aug 5, 2024 at 10:51 PM andrew
wrote:
> Hi,
>
> Due to some pretty major life changes I am retiring
On Tue, 6 Aug 2024, Bob Funk wrote:
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.
OK, take a look now: https://slackbuilds.org/slackbuilds/15.0/SLACKBUILDS.TXT
There were som
I can take care of
* maildrop with courier-unicode
* gimp-plugin-export-layers
* wavbreaker
if no one absolutely wants one of them.
Selon andrew :
> Hi,
>
> Due to some pretty major life changes I am retiring myself from the
> following slackbuilds:
>
> * aom
> * courier-unicode
> *
On Tue, 6 Aug 2024, Bob Funk wrote:
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.
Whatever you're writing that's going to read SLACKBUILDS.TXT, you
could pick apart the md5sum
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 inste
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
I was playing around with making some command line tools for parsing the
SLACKBUILDS.TXT file when I noticed a couple improperly listed MD5SUMs
in the SLACKBUILDS.TXT file.
The 'vst3sdk' slackbuild's md5sum in SLACKBUILDS.TXT is listed as:
SLACKBUILD MD5SUM:
463991d7841d15c719a7e06f052b70af42f
Hello,
I was playing around with making some command line tools for parsing the
SLACKBUILDS.TXT file when I noticed a couple improperly listed MD5SUMs in
the SLACKBUILDS.TXT file.
The 'vst3sdk' slackbuild's md5sum in SLACKBUILDS.TXT is listed as:
SLACKBUILD MD5SUM:
463991d7841d15c719a7e06f052b70a
