all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eric Bavier <ericbavier@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 5/5] gnu: Some cleanup based on lint checkers.
Date: Sun, 26 Oct 2014 10:03:50 -0500	[thread overview]
Message-ID: <87mw8iyisp.fsf@gmail.com> (raw)
In-Reply-To: <87fvebre25.fsf@gnu.org>


Ludovic Courtès writes:

> Eric Bavier <ericbavier@gmail.com> skribis:
>> 2. Many descriptions begin with the package name in lowercase form,
>> which triggers a warning about the description beginning with a
>> lowercase letter.  In this patch I capitalised the package name if I
>> could find a reference to the capital form on the package's home-page
>> somewhere.  Many packages are quite insistent that the package always be
>> referenced by the lowercase name, and I'm not sure how the description
>> would be reworded, or whether it really needs to be.  We could add an
>> exception to the description-starts-with-a-capital-letter rule for when
>> the package name is the first word.
>
> Yes, sounds like a good idea.

I'll do this in an updated patch.

>> 3. Some synopses begin with a numeral, triggering the capital-letter
>> warning.
>
> guile -c '(use-modules(guix)(gnu)(ice-9 regex))(fold-packages (lambda (p r) (if (and (package-synopsis p) (string-match "^[0-9]" (package-synopsis p))) (cons p r) r)) (list))'
>
> returns the empty list.  Which one was it?

E.g. linux-libre, fltk, and cairo.

>> Comments welcome.  Nitpicks especially, since much of this is already
>> quite nitpicky. ;)
>
> I was wondering who was going to take care of that now that we have all
> these fancy checkers, so thank you!  :-)
>
> I skimmed through it and I think you can commit it.  If ‘make
> sync-description’ is unhappy, we should see what’s going on, and
> possibly amend the upstream description if needed.

I forgot about sync-description here.  I will check that.

-- 
Eric Bavier

Please avoid sending me Word or PowerPoint attachments.
See http://www.gnu.org/philosophy/no-word-attachments.html

      reply	other threads:[~2014-10-26 15:01 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-24  5:19 [PATCH 5/5] gnu: Some cleanup based on lint checkers Eric Bavier
2014-10-24 16:05 ` Andreas Enge
2014-10-25 22:06   ` Ludovic Courtès
2014-10-24 18:32 ` Alex Kost
2014-10-25 22:15 ` Ludovic Courtès
2014-10-26 15:03   ` Eric Bavier [this message]

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=87mw8iyisp.fsf@gmail.com \
    --to=ericbavier@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ludo@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.