all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Leo Famulari <leo@famulari.name>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 2/2] gnu: Add espeak.
Date: Wed, 13 Jan 2016 22:27:13 -0500	[thread overview]
Message-ID: <20160114032713.GA7236@jasmine> (raw)
In-Reply-To: <87h9ih4l8n.fsf@gnu.org>

On Wed, Jan 13, 2016 at 03:17:28PM +0100, Ludovic Courtès wrote:
> Leo Famulari <leo@famulari.name> skribis:
> 
> > * gnu/packages/audio.scm (espeak): New variable.
> 
> If you think eSpeak-ng is not ready yet, or is sufficiently different,
> it’s OK to package eSpeak.

I'm looking into it.

> 
> > +    (native-inputs
> > +     `(("unzip" ,unzip)))
> > +    (inputs
> > +      `(("sonic" ,sonic)
> 
> The “unzip” line is misaligned.

The "unzip" line or the "sonic" line? Most of the patches I see use the
former style.

> 
> > +        ("pulseaudio" ,pulseaudio)
> > +        ("portaudio" ,portaudio)))
> 
> Dunno if it’s useful to have both, maybe someone more knowledgeable like
> Ricardo can answer?

I misinterpreted the configure options. It's not useful to have both. If
PulseAudio is an input, then eSpeak will always use PulseAudio unless
configured not to, in which case PulseAudio should not be an input.

PulseAudio stopped working completely on my Debian system a while ago.
I decided to keep using ALSA and never looked back (or is it forward, in
this case? ;)

So, if we are going to target PulseAudio, can a PulseAudio user test
that this package works? This should make the computer speak "hello
world":
$ espeak "hello world"

> 
> > +    (synopsis "Software speech synthesizer")
> > +    (description "eSpeak is a compact software speech synthesizer for
> > +English and other languages, for Linux and Windows.  eSpeak uses a
>                               ^---------------------^
> Remove.

Done.

> 
> In general, we don’t mention proprietary software, and we don’t mention
> other OSes, free or not, portability etc., because that’s not what
> matters from the viewpoint of an OS provider.
> 
> The rest LGTM!

Again, I'll be grateful if a PulseAudio user will test!

> 
> Thanks,
> Ludo’.

  reply	other threads:[~2016-01-14  3:27 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-01-12  5:26 [PATCH 0/2] Add eSpeak Leo Famulari
2016-01-12  5:26 ` [PATCH 1/2] gnu: Add sonic Leo Famulari
2016-01-13 14:10   ` Ludovic Courtès
2016-01-14  3:28     ` Leo Famulari
2016-01-12  5:26 ` [PATCH 2/2] gnu: Add espeak Leo Famulari
2016-01-13 14:17   ` Ludovic Courtès
2016-01-14  3:27     ` Leo Famulari [this message]
2016-01-15  0:38       ` Leo Famulari
2016-01-15 16:15         ` Ludovic Courtès
2016-01-14 12:02     ` Ricardo Wurmus
2016-01-14 13:32       ` Ludovic Courtès
2016-01-17 16:09         ` Ricardo Wurmus
2016-01-17 20:30           ` PulseAudio & ALSA Ludovic Courtès
2016-02-09 21:45             ` Ricardo Wurmus
2016-01-12  5:58 ` [PATCH 0/2] Add eSpeak Leo Famulari
2016-01-12  6:01   ` Leo Famulari
2016-01-12 15:48   ` Andreas Enge
2016-01-12 19:30     ` Leo Famulari
2016-01-13  0:09       ` Leo Famulari
2016-01-13 14:01 ` PulseAudio Ludovic Courtès
2016-02-09 21:26   ` PulseAudio Christopher Allan Webber
2016-02-09 21:35     ` PulseAudio Leo Famulari
2016-02-12  9:12       ` PulseAudio Ludovic Courtès
2016-02-12 10:21         ` PulseAudio Ricardo Wurmus
2016-02-12 11:13           ` PulseAudio Alex Sassmannshausen
2016-02-15  7:38             ` PulseAudio Ricardo Wurmus
2016-02-15  8:56               ` PulseAudio Alex Sassmannshausen
2016-02-09 21:43     ` PulseAudio Ricardo Wurmus
2016-02-09 23:36     ` PulseAudio Jookia

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=20160114032713.GA7236@jasmine \
    --to=leo@famulari.name \
    --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.