On 2023-05-13, Liliana Marie Prikler wrote:
> Am Freitag, dem 12.05.2023 um 18:33 -0700 schrieb Vagrant Cascadian:
>
>> +  %D%/packages/patches/fuzzylite-relative-path-in-tests.patch	\
>> +  %D%/packages/patches/fuzzylite-use-catch2.patch		\
>> +  %D%/packages/patches/fuzzylite-when-testing-large-float-numbers-
>> for-equ.patch	
> Prefer names that don't blow up the file name, e.g. "fuzzylite-fix-
> test", "fuzzylite-soften-float-equality", or "fuzzylite-workaround-
> issue-N" – although I'm not sure whether we have a precedent for the
> latter.

Went with fuzzylite-soften-float-equality. Thanks!


>> +              (patches (search-patches "fuzzylite-use-catch2.patch"
>> +                        "fuzzylite-when-testing-large-float-numbers-
>> for-equ.patch"
>> +                        "fuzzylite-relative-path-in-tests.patch"))))
> This doesn't appear properly indented.

guix style strikes again! Fixed.


>> +    (synopsis "fuzzy logic control binary")
> Capitalize the first word.  IIRC we also allow title case for proper
> names and such, but I don't think that'd be necessary here.

Fixed.


>> +     "fuzzylite is a fuzzy logic control library which allows one
>> +to easily create fuzzy logic controllers in a few steps utilizing
>> +object-oriented programming.")
> Proper sentences start with an uppercase letter.  The convention is to
> use @-constructs when the package name prohibits that.  You can also
> cheat via "This package provides ..."

Went with the cheat. :)


>> +    (license license:gpl3)))
> No +?

I do not see any "or any later version" or similar wording anywhere, no.


>> fuzzylite is a registered trademark of FuzzyLite Limited.
> Perhaps also look into their trademark policy then, if they have any.

Have not found one...


>> +-#include "test/catch.hpp"
>> ++#include "catch2/catch.hpp"
> Use <catch2/catch.hpp> to signal that this is a system header.

I tried applying this, but it failed to build... left it out of this
revision.


live well,
  vagrant