From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: Re: chromaprint: fpcalc missing
Date: Tue, 03 Apr 2018 15:45:50 +0200 [thread overview]
Message-ID: <87in989ze9.fsf@gnu.org> (raw)
In-Reply-To: <876058wlik.fsf@gmail.com> (Pierre Neidhardt's message of "Tue, 03 Apr 2018 17:27:07 +0530")
Hello,
Pierre Neidhardt <ambrevar@gmail.com> skribis:
> Catonano <catonano@gmail.com> writes:
>
>> which package are you talking about ?
>>
>> Anyway, you can submit a patch ☺
>
> The chromaprint package.
>
> I'll submit a patch but I wanted to ask, maybe the original author of
> the recipe has an opinion about it.
The best way to know that is by sending a patch. ;-)
A common criterion in deciding whether or not to enable an optional
feature is how widely used it is vs. how much it adds to the size of the
package closure. If you can provide that kind of info in your patch
submission, that’ll make it easier to decide what to do.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-04-03 13:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-03 6:24 chromaprint: fpcalc missing Pierre Neidhardt
2018-04-03 11:35 ` Catonano
2018-04-03 11:57 ` Pierre Neidhardt
2018-04-03 13:45 ` Ludovic Courtès [this message]
2018-04-03 14:33 ` Pierre Neidhardt
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=87in989ze9.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=ambrevar@gmail.com \
--cc=help-guix@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.
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).