From: Florin Sarbu <florin.sarbu@windriver.com>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: alsaconf and bash
Date: Mon, 7 Jan 2013 23:36:52 +0200 [thread overview]
Message-ID: <50EB3FF4.60601@windriver.com> (raw)
Hi all,
in alsa-utils_1.0.25.bb, I see this comment:
# We omit alsaconf, because
# a) this is a bash script
# b) it creates config files not suitable for OE-based distros
Trying out on master, I get a do_rootfs error because bash is not a
rundep of alsa-utils, and there is nothing in the alsa-utils recipe that
actually does the above mentioned removal of the alsaconf script.
Looking in the git log, I only see that the comment has suddenly
appeared in an older alsa-utils recipe and has been carried along since
with every update to the recipe, and not left over there as an artifact
of some older commit as I expected.
Can anyone shed some light on this?
Thanks,
Florin
next reply other threads:[~2013-01-08 0:15 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-07 21:36 Florin Sarbu [this message]
2013-01-08 0:44 ` alsaconf and bash Chris Larson
2013-01-08 6:09 ` Florin Sarbu
2013-01-08 14:15 ` Florin Sarbu
2013-01-08 16:27 ` Andrei Gherzan
2013-01-08 17:15 ` Florin Sarbu
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=50EB3FF4.60601@windriver.com \
--to=florin.sarbu@windriver.com \
--cc=openembedded-core@lists.openembedded.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