[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
OpenEmbedded recipe
From: |
Luke Yelavich |
Subject: |
OpenEmbedded recipe |
Date: |
Fri, 6 Jun 2014 09:31:30 +1000 |
On Thu, Jun 05, 2014 at 11:39:21PM EST, Otavio Salvador wrote:
> Hello,
>
> We've been working in the recipe for the OpenEmbedded and I'd like to
> split it more in sub-packages as this is critical when using it in
> embedded systems.
>
<Snip>
>
> As I am new to the project I'd like some feedback on how we can move
> the configuration files (where those should be) and how to split the
> client support code.
When you say move the configuration files where they should be, do you mean
that Open Embedded policy is to put them elsewhere? Secondly, does open
embedded have a policy to break out libraries into a separate binary package?
Either way, I suggest you break out the client library into its own binary
package similar to how its done in debian. The binary package in debian is
libspeechd2, where the package name is made up of the library name and the
major number of its soname.
Hope this helps.
Luke