From: Thomas Danckaert <post@thomasdanckaert.be>
To: ludo@gnu.org
Cc: 25836@debbugs.gnu.org
Subject: bug#25836: [PATCH] gnu: Add gspell
Date: Wed, 17 May 2017 17:16:26 +0200 (CEST) [thread overview]
Message-ID: <20170517.171626.2148481571502189736.post@thomasdanckaert.be> (raw)
In-Reply-To: <87a86bwoh9.fsf@gnu.org>
From: ludo@gnu.org (Ludovic Courtès)
Subject: Re: bug#25836: [PATCH] gnu: Add gspell
Date: Wed, 17 May 2017 16:24:18 +0200
>> I'm not really familiar with the gobject system, but I suppose
>> generating the bindings is useful? :)
>
> For now we don’t have any users of gspell at all, let alone users
> of its
> Vala bindings, so perhaps we can leave it as is?
>
> Building the docs to a separate “doc” output could be marginally
> useful,
> I think.
For me, it's me as it is. I have no use for those bindings or the
documentation myself. I just stumbled upon them while trying to
debug the package, and thought I'd mention it just in case.
When I submit a package, I usually try to enable as many options as I
can, even though I don't use them myself, just in case someone might
need them. Maybe this is overkill? Is there a general
recommendation for Guix?
Thomas
next prev parent reply other threads:[~2017-05-17 15:17 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAJ98PDyRmcJEZTC6dOuuwXeH+j6ZtwYnMmtmD-0bj9N9yWfZMg@mail.gmail.com>
[not found] ` <87wpbx9z7b.fsf@gnu.org>
[not found] ` <87vaqwp2l8.fsf_-_@gnu.org>
[not found] ` <alpine.DEB.2.11.1703261253200.2667@intel.home>
2017-03-27 8:26 ` bug#25836: [aspell-devel] Honoring ‘ASPELL_CONF’ in libaspell Ludovic Courtès
2017-05-03 16:49 ` Catonano
2017-05-03 18:14 ` Kevin Atkinson
2017-05-17 14:21 ` Ludovic Courtès
2017-05-17 18:14 ` Kevin Atkinson
2017-03-30 11:57 ` bug#25836: [PATCH] gnu: Add gspell Thomas Danckaert
2017-03-30 12:08 ` Catonano
2017-05-17 14:24 ` Ludovic Courtès
2017-05-17 15:16 ` Thomas Danckaert [this message]
2017-05-17 19:56 ` Ludovic Courtès
2017-05-17 17:22 ` Catonano
2017-05-17 17:24 ` Catonano
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=20170517.171626.2148481571502189736.post@thomasdanckaert.be \
--to=post@thomasdanckaert.be \
--cc=25836@debbugs.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.