Hartmut Goebel <h.goebel@crazy-compilers.com> writes:

> Am 05.11.2016 um 13:55 schrieb Marius Bakke:
>> +(define-public fatfsck/static
>> +  (package
>> +    (name "fatfsck-static")
>
> What is the reason for using a different name in "define"?

I mostly followed the convention of the e2fsck package. I've seen this
convention elsewhere as well, but don't know the reasoning behind it :)

However fatfsck could perhaps be renamed to dosfsck to better match
the e2fsprogs->e2fsck transformation.