From: Steffen Sledz <sledz@dresearch.de>
To: openembedded-devel@lists.openembedded.org
Subject: Re: [PATCH v2] alsa-lib: fix packaging error
Date: Tue, 11 Jan 2011 15:57:51 +0100 [thread overview]
Message-ID: <4D2C6FEF.7030506@dresearch.de> (raw)
In-Reply-To: <1294756588.4307.7668.camel@mill.internal.reciva.com>
Am 11.01.2011 15:36, schrieb Phil Blundell:
> On Tue, 2011-01-11 at 14:26 -0500, Steffen Sledz wrote:
>> * symlink libasound.so -> libasound.so.2.0.0 in /usr/lib was missing in
>> dev package
>
> Why doesn't the generic FILES_${PN}-dev from bitbake.conf catch this
> file? Not that I think your patch is necessarily wrong but it isn't
> obvious to me why it is necessary.
The ALSA package structure seems to be a bit complex. There is an additional package named libasound but no libasound-dev. The development stuff is summed up in alsa-lib-dev.
BTW: I'm not an ALSA maintainer. Just tumbled over the missing symlink.
Steffen
next prev parent reply other threads:[~2011-01-11 14:58 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <ighiieMAN_POSIXLY_CORRECT=1@dough.gmane.org>
2011-01-11 19:26 ` [PATCH v2] alsa-lib: fix packaging error Steffen Sledz
2011-01-11 13:39 ` Koen Kooi
2011-01-11 14:24 ` Paul Menzel
2011-01-11 14:58 ` Steffen Sledz
2011-01-11 14:36 ` Phil Blundell
2011-01-11 14:57 ` Steffen Sledz [this message]
2011-01-12 7:46 ` Khem Raj
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=4D2C6FEF.7030506@dresearch.de \
--to=sledz@dresearch.de \
--cc=openembedded-devel@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.