<html>
<head>
<meta content="text/html; charset=UTF-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 01/08/2013 02:44 AM, Chris Larson
wrote:<br>
</div>
<blockquote
cite="mid:CABcZAN=nVVoNxdu7tZKQ=uK5Q7jcCrhvFezX-YYpyWPZbTw9jg@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
<div dir="ltr">
<div class="gmail_extra">On Mon, Jan 7, 2013 at 2:36 PM, Florin
Sarbu <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:florin.sarbu@windriver.com" target="_blank">florin.sarbu@windriver.com</a>></span>
wrote:<br>
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0px 0px 0px
0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div id=":10h">in <a moz-do-not-send="true"
href="http://alsa-utils_1.0.25.bb" target="_blank">alsa-utils_1.0.25.bb</a>,
I see this comment:<br>
<br>
# We omit alsaconf, because<br>
# a) this is a bash script<br>
# b) it creates config files not suitable for OE-based
distros<br>
<br>
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.<br>
Can anyone shed some light on this?<br>
</div>
</blockquote>
</div>
<br>
<br clear="all">
<div style="">From some quick git log -S commands in the old
openembedded classic repository, it seems to have originated
with 7653e980f66b4bd147df308f9b04d6b197382d6a from 2005, and
the line below the comment was 'FILES_${PN} = ""', so
presumably that was what left it out — none of the files
patterns matched it.</div>
</div>
</div>
</blockquote>
Okay, so it seems that the comment actually said at that time that
the alsa-utils generated rpm won't contain alsaconf. And bellow,
this bash script gets into the alsa-utils-alsaconf rpm.
Unfortunately, even though there is this separation, the alsa-utils
rpm depends on the alsa-utils-alsaconf rpm so it's pretty much the
same thing as do_rootfs is concerned. (missing bash dependency). How
would you guys see this resolved upstream? Add bash as a dep, remove
alsa-utils-alsaconf as a dep or alsa-utils (as the comment says the
script is not suitable for OE-based distros) or check the alsaconf
script for bashisms and fix if any and make alsa-utils rely on a
busybox shell interpreter if possible (with the modification of the
!/bin/bash shabang from the alsaconf script to /bin/sh)?<br>
<br>
Florin<br>
<br>
<blockquote
cite="mid:CABcZAN=nVVoNxdu7tZKQ=uK5Q7jcCrhvFezX-YYpyWPZbTw9jg@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
-- <br>
Christopher Larson</div>
</div>
</blockquote>
<br>
</body>
</html>