Many thanks to Andreas for detailed comments about licenses. Ludovic Courtès (2014-09-25 16:56 +0400) wrote: > Alex Kost 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? 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: , 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, ...) Also (as I'm writing about synopses): is there a convention to begin a synopsis with a capital letter? There are synopses beginning with a small letter (not counting synopses beginning with a package name): gnome-vfs, cdparanoia, signing-party, ... 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). > 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 :-) Thanks. The modified patch is attached. Good enough?