From: Hartmut Goebel <h.goebel@crazy-compilers.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: 23/36: gnu: Add libkdepim.
Date: Wed, 5 Feb 2020 10:31:41 +0100 [thread overview]
Message-ID: <a6b89325-4ff6-7989-d4a8-b192f1b2d7dc@crazy-compilers.com> (raw)
In-Reply-To: <875zgmugtx.fsf@gnu.org>
Am 04.02.20 um 23:29 schrieb Ludovic Courtès:
> This must get us close to full coverage of the core of KDE, no?
Well, nor t yet. I have yet another approx. 100 packages hanging around.
>> + (synopsis "Libraries for common kdepim apps")
>> + (description "Libraries for common kdepim apps.")
> I know it’s no fun, but could you try to follow the guidelines for
> synopses and descriptions at:
Whet exactly is your point? I assume it is that summary and description
are quite meaningless. I agree on this.
I'm afraid, there is nothing to say about some of these packages. They
are used by KDE PIM only, there is no Readme and no description. Debian
also does not provide more infos.
The only change which makes sense IMHO is to add something like "This
library is used by KDE PIM" to the description. (Or change the
description to only state this.)
WDYT?
--
Regards
Hartmut Goebel
| Hartmut Goebel | h.goebel@crazy-compilers.com |
| www.crazy-compilers.com | compilers which you thought are impossible |
next prev parent reply other threads:[~2020-02-05 9:31 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200203134554.28985.49673@vcs0.savannah.gnu.org>
[not found] ` <20200203134603.BDAB420A10@vcs0.savannah.gnu.org>
2020-02-04 22:29 ` 23/36: gnu: Add libkdepim Ludovic Courtès
2020-02-05 9:31 ` Hartmut Goebel [this message]
2020-02-07 20:47 ` Ludovic Courtès
2020-03-02 9:17 ` Hartmut Goebel
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=a6b89325-4ff6-7989-d4a8-b192f1b2d7dc@crazy-compilers.com \
--to=h.goebel@crazy-compilers.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.