From: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH] mpdstate: add package
Date: Fri, 17 Jun 2016 10:36:00 +0200 [thread overview]
Message-ID: <20160617083600.GA6429@airbook.newtec.eu> (raw)
In-Reply-To: <20160612215336.06191b9e@free-electrons.com>
> Hello,
>
> On Mon, 30 May 2016 08:36:56 +0200, Kurt Van Dijck wrote:
> > Mpdstate listens for MPD state changes and outputs them
> > on stdout. It is easy to write a script that receives mpdstate's output
> > on stdin an act upon some of the events.
> >
> > Signed-off-by: Kurt Van Dijck <dev.kurt@vandijck-laurijssen.be>
>
> Isn't the same thing achievable with the "mpc idle" feature, which
> allows you to listen for events from mpd ?
'mpc idleloop' prints the category of events, certainly not the real
changes.
>
> Like your other package, I'd prefer to have some evidence of even some
> limited adoption/usage of a software package before adding it to
> Buildroot.
Like my other package, mpc is ideal for interactive use, but not for
small automation stuff.
I created a raspberry pi box that engages the audio amplifier whenever
mpd plays, and standby when mpd pauses/stops.
It's hard to build stable scripts around 'mpc' for that regards,
as you need several calls, and the state may change in between.
mpdstate fixes that flow.
Like my other package, I may need to add that kind of comments, I
learned that, and you're right in pointing me to that.
I'm yet puzzled by the version info that I take from the git repository,
that does not work in buildroot since it's buildroot's git repo there.
I haven't found a solution yet, and that's keeping me from updating my
patches :-)
Thanks for the review, I'll take that into account.
Kurt
next prev parent reply other threads:[~2016-06-17 8:36 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-30 6:36 [Buildroot] [PATCH] mpdstate: add package Kurt Van Dijck
2016-06-12 19:53 ` Thomas Petazzoni
2016-06-17 8:36 ` Kurt Van Dijck [this message]
2016-06-17 8:41 ` Thomas Petazzoni
2016-06-19 16:43 ` Ben Boeckel
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=20160617083600.GA6429@airbook.newtec.eu \
--to=dev.kurt@vandijck-laurijssen.be \
--cc=buildroot@busybox.net \
/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