busybox as dynamic lib

[Jan Kiszka]

Rob Landley wrote:
> ...
> Anyway, once standalone is in, the dynamic library allows some of the lost 
> space from the different packaging choice to be reclaimed, by letting the 
> individual apps share some common code.  It's still not as efficient as the 
> one-big-binary approach, but it's another packaging choice (like building a 
> static binary) that gives people more options.

Is there any time schedule for this feature?

On my Embedded SELinux journey I just learned that I need certain
binaries stand-alone in order to apply the policy correctly (e.g. init
or the modutils). Splitting up an existing .config and running make +
further scripting stuff on those fragments sounds like some work, and I
don't like to start this right now when there are alternatives in sight.
Maybe I could even invest some of the gained time in a generic solution
for busybox...

Jan

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 250 bytes
Desc: OpenPGP digital signature
Url : http://lists.busybox.net/pipermail/busybox/attachments/20060220/92ec094c/attachment.pgp