On Tue, Sep 20, 2011 at 1:24 PM, Daniel Lazzari <dlazz...@leapfrog.com> wrote:
>> On 9/20/11 2:03 PM, Daniel Lazzari wrote:
>> > I noticed a problem with the alsa-utils package where the alsa-utils
>> > package does not depend on all of the little extra packages it's supposed
>> > to pull in. I'm not sure what the best way to fix this is though. Can
>> > anyone give me a little guidance or point me at a recipe that does this
>> > correctly already?
>>
>> If you are using the RPM backend, I'm currently working on something that may
> resolve this issue for you. Hopefully ready today.
>>
>> Otherwise, switch to ipk or deb and see if you get the same behavior.
>
> I'm using ipk already.
>
>> I don't see why this is a problem, personally. If someone wants a recipe's
>> main package to depend on the other packages it emits, they're free to make
>> the recipe do so. But the ${PN} package is not defined to include everything
>> from the recipe, it never has been.
>
> I understand that. With the alsa-utils package, the recipe specifically
> mentions
> # This are all packages that we need to make. Also, the now empty alsa-utils
> # ipk depends on them.
>
> Right above adding packages such as "alsa-utils-alsamixer" to the PACKAGES
> variable. I need all of those more specific packages and if I understand
> correctly, I should be able to get them by just adding the "alsa-utils"
> package to my custom image.
Sounds like it's just a recipe bug then, if it claims to do something
which it doesn't do.
--
Christopher Larson
clarson at kergoth dot com
Founder - BitBake, OpenEmbedded, OpenZaurus
Maintainer - Tslib
Senior Software Engineer, Mentor Graphics
_______________________________________________
Openembedded-core mailing list
Openembedded-core@lists.openembedded.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/openembedded-core
