all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Roel Janssen <roel@gnu.org>
To: Andreas Enge <andreas@enge.fr>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: [PATCH] gnu: Add perltidy.
Date: Sun, 10 Jul 2016 12:48:30 +0200	[thread overview]
Message-ID: <87eg71n4zl.fsf@gnu.org> (raw)
In-Reply-To: <20160709190125.GA31432@solar>


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

  reply	other threads:[~2016-07-10 10:48 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05  8:54 [PATCH] gnu: Add perltidy Roel Janssen
2016-07-05 11:01 ` Ricardo Wurmus
2016-07-05 11:10   ` Roel Janssen
2016-07-05 13:57     ` Ricardo Wurmus
2016-07-05 14:15       ` Roel Janssen
2016-07-09 19:01   ` Andreas Enge
2016-07-10 10:48     ` Roel Janssen [this message]
2016-07-10 13:27       ` Andreas Enge

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87eg71n4zl.fsf@gnu.org \
    --to=roel@gnu.org \
    --cc=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.