All of lore.kernel.org
 help / color / mirror / Atom feed
From: Marcin Juszkiewicz <openembedded@hrw.one.pl>
To: openembedded-devel@lists.openembedded.org
Subject: RFC: More granular libraries packaging
Date: Fri, 27 Oct 2006 18:01:51 +0200	[thread overview]
Message-ID: <200610271801.52172.openembedded@hrw.one.pl> (raw)


One of our strong points is granular packaging. We have extra packages for 
locales, documentation, development stuff etc. But we can improve it a bit 
more.

Many packages has multiple libraries in package. Not everytime it is 
useful - for example libusb had dependency on libstdc++ just because it 
had libusbpp in same package as libusb.

My proposition is - let split each library to separate package. This will 
enlarge feeds (so ipkg will get hurt more ;( but in some situations can 
give us smaller rootfs.

Probably best solution to get this done will be some extra code in 
package_ipk.bbclass.

Example of package to 'fix' is obexftp:

NOTE: Multiple libraries (libbfb.so.0, libcobexbfb.so.0, libcobexpe.so.0, 
libobexftp.so.0) found and LEAD_SONAME not defined
Packaged contents of obexftp 
into /home/hrw/devel/build/3541-feed/tmp/deploy/ipk/obexftp_0.10.3-r1_arm.ipk


-- 
JID: hrw-jabber.org
OpenEmbedded developer/consultant

   Fear leads to anger, anger leads to hate, hate... leads to suffering.
   		-- Yoda





             reply	other threads:[~2006-10-27 16:02 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-27 16:01 Marcin Juszkiewicz [this message]
2006-10-27 19:43 ` RFC: More granular libraries packaging Michael 'Mickey' Lauer
2006-10-28  1:12   ` Øyvind Repvik
2006-10-31 16:17 ` Richard Purdie

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=200610271801.52172.openembedded@hrw.one.pl \
    --to=openembedded@hrw.one.pl \
    --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.