unofficial mirror of guix-patches@gnu.org 
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: Andy Tai <atai@atai.org>
Cc: 46393@debbugs.gnu.org
Subject: [bug#46393] [PATCH] gnu: Add ocrfeeder
Date: Sat, 20 Feb 2021 19:33:56 -0500	[thread overview]
Message-ID: <YDGqdMyoaVL0qrmQ@jasmine.lan> (raw)
In-Reply-To: <CAJsg1E-Lm1znYh6N9vhP9Uaa4hEB07WhjpGHqtxS-ppX1kE6Bw@mail.gmail.com>

On Sat, Feb 13, 2021 at 06:40:57PM -0800, Andy Tai wrote:
> * gnu/packages/gnome.scm (ocrfeeder): New variable
> * gnu/packages/python-xyz.scm (python-sane): New variable

In general, we add packages one commit at a time, so we prefer to
receive this as two patches. First, a patch that adds python-sane, and
then a second patch adding ocrfeeder.

> +(define-public ocrfeeder

Overall LGTM, thanks!

> +    (synopsis "A Complete OCR Suite")

I would write, simply, "Complete OCR Suite". For some reason, the linter
doesn't complain for me, but it should recommend against starting
synopses with an article. That is, with "a", "an", or "the".

https://guix.gnu.org/manual/en/html_node/Synopses-and-Descriptions.html

> +    (description "OCRFeeder is a complete Optical Character
> Recognition and Document Analysis and Recognition program")

And make sure to end the sentence with a period "."

> +(define-public python-sane

Great!

> +    (synopsis "Python interface to the SANE scanner")
> +    (description "Python interface to the SANE scanner and frame
> grabber interface for Linux")

We prefer to use complete sentences in the description. You can always
make it simple:

"This package provides Python interface to the SANE scanner and frame
grabber interface for Linux."

> +    (license license:expat)))

I looked in the repo and it doesn't look like the expat license:

https://directory.fsf.org/wiki/License:Expat

I'm not sure what it is? Can you do a little research? That FSF license
directory might help.




  reply	other threads:[~2021-02-21  0:35 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-09  3:54 [bug#46393] [PATCH] gnu: Add ocrfeeder Andy Tai
     [not found] ` <handler.46393.B.161284293412235.ack@debbugs.gnu.org>
2021-02-14  2:40   ` Andy Tai
2021-02-21  0:33     ` Leo Famulari [this message]
2021-02-21  6:37       ` Andy Tai
2021-02-22 18:27         ` Leo Famulari
2021-02-22 18:29           ` Andy Tai
2021-02-21  7:09       ` Andy Tai
2021-02-23 20:00         ` Leo Famulari
2021-02-23 20:05         ` Leo Famulari
2021-02-23 20:22           ` Andy Tai
2021-02-24  1:59             ` Andy Tai
2021-02-24  2:09               ` Andy Tai
2021-02-24 16:08                 ` bug#46393: " Leo Famulari
2021-02-24 19:04                   ` [bug#46393] " Andy Tai

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=YDGqdMyoaVL0qrmQ@jasmine.lan \
    --to=leo@famulari.name \
    --cc=46393@debbugs.gnu.org \
    --cc=atai@atai.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 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).