From: Xinglu Chen <public@yoctocell.xyz>
To: Gabriel Wicki <gabriel@erlikon.ch>, 48630@debbugs.gnu.org
Subject: [bug#48630] [PATCH] adds `ack' package and it's perl module dependency File::Next
Date: Mon, 24 May 2021 23:26:22 +0200 [thread overview]
Message-ID: <87mtsj962p.fsf@yoctocell.xyz> (raw)
In-Reply-To: <20210524191054.7wtb4wopstgx2c77@silver>
[-- Attachment #1: Type: text/plain, Size: 3016 bytes --]
On Mon, May 24 2021, Gabriel Wicki wrote:
> modified: gnu/packages/perl.scm
> - adds package `perl-file-next' (module File::Next)
>
> modified: gnu/packages/textutils.scm
> - adds package `ack' with disabled tests
Commit messages should be written in ChangeLog format[1], you can look
at previous commits for examples.
This commit should also be split into two separate commits, one adding
‘perl-file-next’, and the other adding ‘ack’.
> +(define-public perl-file-next
> + (package
> + (name "perl-file-next")
> + (version "1.18")
> + (source (origin
> + (method git-fetch)
> + (uri (git-reference
> + (url "https://github.com/petdance/file-next")
> + (commit version)))
> + (file-name "perl-next-file")
Use ‘(file-name (git-file-name name version))’.
> + (sha256
> + (base32
> + "0zdrxk409qxkbbv4fl4wi285kfzyrpaja9wfl00vrxc078rs4afm"))))
> + (build-system perl-build-system)
> + (synopsis "File::Next is a lightweight, taint-safe file-finding Perl module")
Try to make the synopsis as concise as possible, just “Lightweight,
taint-safe file-finding Perl module” should do. See the ‘Synopses and
Descriptions’ section of the manual.
> + (description "A Perl CPAN module for finding files. It has no non-core
> +prerequisites")
The description should contain one or more complete sentences.
> +(define-public ack
> + (package
> + (name "ack")
> + (version "3.5.0")
> + (source (origin
> + (method git-fetch)
> + (uri
> + (git-reference
> + (url "https://github.com/beyondgrep/ack3")
> + (commit (format #nil "v~a" version))))
We usually use ‘(string-append "v" version)’ instead of ‘format’.
> + (file-name "ack")
Use ‘(file-name (git-file-name name version))’ (same as above).
> + (sha256
> + (base32 "00131vqjbzcn6w22m0h3j6x9kp59dimfnnqhpmi78vbcj0jws1dv"))))
> + (build-system perl-build-system)
> + (arguments '(#:tests? #f))
What’s the reason for disabling the tests?
> + (propagated-inputs `(("perl-file-next" ,perl-file-next)))
> + (synopsis "Code-searching tool optimized for programmers with large trees
> +of source code")
> + (description "ack is a tool for finding text inside files. it is designed for
^^
Please use double spacing, and capitalize.
> +hackers and programmers by being fast, ignoring VCS directories, letting a user
> +easily specify file types, match highlighting, Perl-Compatible Regular
> +Expressions, and being faster to type than `grep '")
^^
Unecessary whitespace, and missing period.
Could you send an updated series?
[1]: https://www.gnu.org/prep/standards/html_node/Change-Logs.html#Change-Logs
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 861 bytes --]
next prev parent reply other threads:[~2021-05-24 21:27 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-24 19:10 [bug#48630] [PATCH] adds `ack' package and it's perl module dependency File::Next Gabriel Wicki
2021-05-24 21:01 ` Maxime Devos
2021-05-24 21:26 ` Xinglu Chen [this message]
[not found] ` <handler.48630.B.162188348523111.ack@debbugs.gnu.org>
2021-05-25 19:12 ` [bug#48630] Acknowledgement ([PATCH] adds `ack' package and it's perl module dependency File::Next) Gabriel Wicki
2021-05-25 21:34 ` Xinglu Chen
2021-05-25 22:03 ` [bug#48630] [PATCH] adds `ack' package and it's perl module dependency File::Next Gabriel Wicki
2021-07-26 14:33 ` [bug#48630] Acknowledgement ([PATCH] adds `ack' package and it's perl module dependency File::Next) Gabriel Wicki
2021-05-25 22:13 ` [bug#48630] [PATCH] adds `ack' package and it's perl module dependency File::Next Gabriel Wicki
2021-05-27 6:45 ` Xinglu Chen
2021-05-27 16:45 ` Gabriel Wicki
2021-05-28 20:13 ` Xinglu Chen
2021-07-06 18:52 ` Gabriel Wicki
2022-07-08 16:44 ` bug#48630: " Ricardo Wurmus
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87mtsj962p.fsf@yoctocell.xyz \
--to=public@yoctocell.xyz \
--cc=48630@debbugs.gnu.org \
--cc=gabriel@erlikon.ch \
/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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).