From: ludo@gnu.org (Ludovic Courtès)
To: Alex Kost <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/3] gnu: Add imlib2.
Date: Thu, 25 Sep 2014 21:01:37 +0200 [thread overview]
Message-ID: <87zjdned7y.fsf@gnu.org> (raw)
In-Reply-To: <87h9zvd2kx.fsf@gmail.com> (Alex Kost's message of "Thu, 25 Sep 2014 21:36:46 +0400")
Alex Kost <alezost@gmail.com> skribis:
> Many thanks to Andreas for detailed comments about licenses.
>
> Ludovic Courtès (2014-09-25 16:56 +0400) wrote:
>
>> Alex Kost <alezost@gmail.com> skribis:
>>
>>> +(define-public imlib2
>>
>> [...]
>>
>>> + (home-page "http://sourceforge.net/projects/enlightenment/")
>>> + (synopsis
>>> + "Library for loading, saving, rendering and manipulating image files")
>>
>> s/Library for//
>
> Done. Is there any convention about that?
Not really. The one above didn’t fit on the line, so I thought it would
make sense to strip a couple of words. :-)
We should add a linter making sure the synopsis doesn’t exceed a certain
length, 60 characters, say.
> I'm asking because there are several "types" of synopses:
>
> - Several synopses begin with "Library for" (libuv, fontconfig,
> lightning, ...)
>
> - Few ones begin with "Library to" (cloog, petsc, ...)
>
> - Some packages have the following synopsis structure:
>
> <package-name>, a library ...
>
> Some of them begin with a capital letter (libjpeg, libgpg-error,
> freetype, ...), and some with a small one (fpill, libogg, libpaper, ...)
>
> - Many synopses end with "library" (libsamplerate, clucene, libgcrypt, ...)
Synopses starting with the package name are definitely frowned upon (we
should add a linter for that.) The others listed above may or may not
be OK, depending.
> Also (as I'm writing about synopses): is there a convention to begin a
> synopsis with a capital letter?
Yes. Another linter needed!
> Also there are 2 packages with synopses beginning with an article:
> “pkg-config” and “id3lib”, but it's a lower-case article (perhaps "guix
> lint" should be adjusted for this case).
Yes.
>> Actually this should probably go to (gnu packages image), which is home
>> for all its friends.
>
> OK, initially I wanted to put it there, but then I found that “giflib”
> is in a separate file, so I thought that maybe "image.scm" contains some
> special image libraries.
>
> If “giflib” also should be put in "image.scm", please don't move it
> there before I push these imlib2/giblib commits :-)
Fine. :-)
> From 11c8f170a0f3c8f5f4ed4730681224de46745d62 Mon Sep 17 00:00:00 2001
> From: Alex Kost <alezost@gmail.com>
> Date: Thu, 25 Sep 2014 12:27:25 +0400
> Subject: [PATCH 1/3] gnu: Add imlib2.
>
> * gnu/packages/image.scm (imlib2): New variable.
Perfect!
Thanks for tolerating and even encouraging nitpicking. ;-)
Ludo’.
next prev parent reply other threads:[~2014-09-25 19:02 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-25 8:53 [PATCH 1/3] gnu: Add imlib2 Alex Kost
2014-09-25 12:44 ` Andreas Enge
2014-09-25 12:54 ` Ludovic Courtès
2014-09-25 12:49 ` Andreas Enge
2014-09-25 12:56 ` Ludovic Courtès
2014-09-25 17:36 ` Alex Kost
2014-09-25 19:01 ` Ludovic Courtès [this message]
2014-09-29 20:00 ` [PATCH] gnu: Move giflib to (gnu packages image) Alex Kost
2014-09-29 21:22 ` Ludovic Courtès
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=87zjdned7y.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--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 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).