Hello All,
I've been comparing some OpenPKG rpms against rpms from other RPM distributions. One thing I hadn't noticed before is that (at least with Postfix) the resultant binary packages are much larger than their native equivalents[1]. This appears to be due to the fact that many libraries are "mainly" statically rather than dynamically linked. Is this intentional?
This can make a large file/memory usage difference especially for long running server processes which use multiple instances (apache?).
Perhaps the issue is ensuring native libXXXX libraries do not configure with OpenPKG installed equivalent libXXXX libraries?
Is it possible to enable/disable this behaviour either at a package or system level, and if not would it be interesting to be able to configure this sort of functionality? Perhaps doing this generically on different platforms makes this task much more difficult.
Thanks for any ideas.
Regards,
Simon Mudd
[1] My RHEL3 Postfix 2.1.4 RPMs occupy, see http://postfix.WL0.org/ftp/official/2.1/ -rw-r--r-- 1 sjmudd sjmudd 3037979 Jul 28 19:56 postfix-2.1.4-4.rhel3.i386.rpm -rw-r--r-- 1 sjmudd sjmudd 2562632 Jul 28 19:41 postfix-2.1.4-4.src.rpm
My OpenPKG Postfix 2.1.4 RPMs occupy (minimal patch added) -rw-r--r-- 1 root root 12900797 Aug 25 21:27 postfix-2.1.4-2.1.3.ix86-rhel3.0-ope.rpm -rw-r--r-- 1 root root 2289591 Aug 25 21:27 postfix-2.1.4-2.1.3.src.rpm
The binary RPMs are 4x larger! ______________________________________________________________________ The OpenPKG Project www.openpkg.org User Communication List [EMAIL PROTECTED]
