From: joey-commits <joey-commits@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: pcaudiolib
Date: Mon, 16 Nov 2020 17:13:02 +0100 [thread overview]
Message-ID: <20201116161302.PPZcz0zUgghZIWrrPGCqrxlHWxT4sOnURhlGIScXcF4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-26384@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 938 bytes --]
New comment by joey-commits on void-packages repository
https://github.com/void-linux/void-packages/pull/26384#issuecomment-728162370
Comment:
Ideally, espeak users could be moved to espeak-ng since the former is unmaintained, but this will take some careful planning to prevent breakage. I know for a fact that speech dispatcher has weird issues when it is built against espeak-ng and espeak at the same time. Also, espeak-ng and espeak cannot coexist on the same system because espeak-ng ships compat links so that older packages supporting espeak can be built against espeak-ng. Another minor issue is an espeakup build issue, but that can be built against espeak-ng with minor changes to its makefile. Sonic is used by espeak-ng for faster speech rates. Just curious, did my packaging sonic cause you to create this pr or was it purely coincidental? As far as I know, espeak-ng is the only thing using libsonic and pcaudiolib etc.
next prev parent reply other threads:[~2020-11-16 16:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-14 20:03 [PR PATCH] " skmpz
2020-11-16 15:34 ` joey-commits
2020-11-16 15:46 ` skmpz
2020-11-16 15:46 ` [PR PATCH] [Closed]: " skmpz
2020-11-16 16:13 ` joey-commits [this message]
2020-11-16 19:51 ` skmpz
2020-11-16 20:01 ` joey-commits
2020-11-16 20:02 ` joey-commits
2020-11-16 21:13 ` joey-commits
2020-11-16 22:06 ` joey-commits
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=20201116161302.PPZcz0zUgghZIWrrPGCqrxlHWxT4sOnURhlGIScXcF4@z \
--to=joey-commits@users.noreply.github.com \
--cc=ml@inbox.vuxu.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 NNTP newsgroup(s).