Openembedded Core Discussions
 help / color / mirror / Atom feed
From: Florin Sarbu <florin.sarbu@windriver.com>
To: <openembedded-core@lists.openembedded.org>
Subject: Re: alsaconf and bash
Date: Tue, 8 Jan 2013 16:15:05 +0200	[thread overview]
Message-ID: <50EC29E9.7000500@windriver.com> (raw)
In-Reply-To: <50EBB80A.2090704@windriver.com>

[-- Attachment #1: Type: text/plain, Size: 2525 bytes --]

Would you guys suggest we add bash as a dependency for alsa-utils?

On 01/08/2013 08:09 AM, Florin Sarbu wrote:
> On 01/08/2013 02:44 AM, Chris Larson wrote:
>> On Mon, Jan 7, 2013 at 2:36 PM, Florin Sarbu 
>> <florin.sarbu@windriver.com <mailto:florin.sarbu@windriver.com>> wrote:
>>
>>     in alsa-utils_1.0.25.bb <http://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?
>>
>>
>>
>> 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.
> 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)?
>
> Florin
>
>> -- 
>> Christopher Larson
>
>
>
> _______________________________________________
> Openembedded-core mailing list
> Openembedded-core@lists.openembedded.org
> http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core


[-- Attachment #2: Type: text/html, Size: 4759 bytes --]

  reply	other threads:[~2013-01-08 14:30 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-07 21:36 alsaconf and bash Florin Sarbu
2013-01-08  0:44 ` Chris Larson
2013-01-08  6:09   ` Florin Sarbu
2013-01-08 14:15     ` Florin Sarbu [this message]
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=50EC29E9.7000500@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