Holger Levsen hol...@layer-acht.org writes:
For the future, I think it would make sense to release a new 1.1 of
saytime, and include all those debian patches, what do you think?
I haven't looked through all the other patches, but if we're likely the
new upstream, then I doubt it's likely to be
Hi Rob,
(sorry for the delay...)
On Samstag, 3. März 2012, Rob Browning wrote:
OK, then here are some initial patches. I've also included checks for
unexpected arguments, and support (assuming ?= is ok) for overriding
CFLAGS. Let me know if you see anything you'd like fixed.
thanks, I've
On Samstag, 3. März 2012, Rob Browning wrote:
By the way -- does saytime still have an upstream that might also care
about any of this?
AFAICS, saytime is dead upstream. So you are free to become the new upstream
;)
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with
Holger Levsen hol...@layer-acht.org writes:
On Samstag, 3. März 2012, Rob Browning wrote:
By the way -- does saytime still have an upstream that might also care
about any of this?
AFAICS, saytime is dead upstream. So you are free to become the new upstream
OK, then how about this:
- Use
Hi Rob,
On Samstag, 3. März 2012, Rob Browning wrote:
OK, then how about this:
sounds good to me.
Of course, it also makes sox even more overtly dependent on sox, but the
alternative is to hard-code/validate the backend set, which I'm not sure
is better.
indeed.
Thanks
thank you! :-)
Holger Levsen hol...@layer-acht.org writes:
sounds good to me.
OK, then here are some initial patches. I've also included checks for
unexpected arguments, and support (assuming ?= is ok) for overriding
CFLAGS. Let me know if you see anything you'd like fixed.
From
Ariel asdeb...@dsgml.com writes:
On Thu, 1 Mar 2012, Rob Browning wrote:
If we want -b [foo], I'll need to specify b to getopt (no colons)
and handle any subsequent oss|alsa value manually (increment optind,
etc.). That works -- or we can just require -balsa/-boss.
Are you sure about that
Holger Levsen hol...@layer-acht.org writes:
Of course, if we didn't have to worry about backward compatibility at
all,
I think we don't. Saytime wasnt included in squeeze (sadly) anyway,
so...
Hmm, I'd still be tempted to care somewhat if it doesn't cost too much.
I have any number of
Hi Bob,
On Donnerstag, 1. März 2012, Rob Browning wrote:
So somehow I missed Ariel and your earlier messages, but I'm poking at
this again now...
:-)
Of course, if we didn't have to worry about backward compatibility at
all,
I think we don't. Saytime wasnt included in squeeze (sadly)
On Thu, 1 Mar 2012, Rob Browning wrote:
Ariel asdeb...@dsgml.com writes:
I had thought that getopt() supported -b [foo] style arguments, but
I must have misremembered. It looks like it only supports -b[foo].
If we want -b [foo], I'll need to specify b to getopt (no colons)
and handle any
So somehow I missed Ariel and your earlier messages, but I'm poking at
this again now...
Ariel asdeb...@dsgml.com writes:
Just do -d instead of -t alsa and it will pick the output device
automatically.
Nice. I hadn't noticed -d.
I would structure it like this:
If nothing is passed to -b
Hi Ariel,
On Freitag, 25. Juni 2010, Ariel wrote:
Rob - you are working way too hard to determine the sox output device.
[...]
I wonder if this message will reach you considering the bug is from 3
years ago.
I could probably fix up this patch myself if you like.
I've took over saytime
Rob - you are working way too hard to determine the sox output device.
Just do -d instead of -t alsa and it will pick the output device
automatically.
I would structure it like this:
If nothing is passed to -b then use -d in sox, and -o is ignored.
If an option is passed to -b then use it,
13 matches
Mail list logo
