Andreas Enge writes: > Hello, > > sorry for being late, but the number of messages on the list is simply > overwhelming...
Thanks for your reply :) > On Tue, Jul 05, 2016 at 01:01:07PM +0200, Ricardo Wurmus wrote: >> “perltidy” (as in the domain name) or “perl-tidy” (as in the tarball)? >> I don’t remember what our naming guidelines say about this. (I think >> “perltidy” is correct.) > > Is it a perl "module"? Then it should be named "perl-tidy": > > https://www.gnu.org/software/guix/manual/html_node/Perl-Modules.html#Perl-Modules > If it is a perl "binary", then keeping the upstream name is the good solution. > > In this case, maybe the latter holds? There is a ready-to-use perl script, but > also a file Tidy.pm. >From the man-page of "perltidy": Perltidy reads a perl script and writes an indented, reformatted script. So even though it does provide a Perl::Tidy module, it's also a stand-alone program that reformats existing Perl code. What we could to is split the package in two: one with the Perl::Tidy module (called perl-tidy) and one with the stand-alone script (called perltidy). I think that would be a little confusing though. Kind regards, Roel Janssen
