I too have felt this sting. I currently compile a custom version of Postfix against the CentOS repo Mysql libraries. So any security patches send me into a compiling frenzy when I update my server. I'm a big fan of packages containing all files needed to run the package, so static linking. But you have a point that they will tend to be larger and may be more insecure. You're other point is good about dynamic linking. Better security from updates, but when one package is updated, many others may have to be updated to satisfy the new patches.
So, in my opinion, I think it comes down to who is maintaining those packages and the amount of work you are willing to spend on them. If you don't mind recompiling all the packages then Dynamic is the best. For simplicity, Static is better. I guess I would have to say I'm in favor of dynamic. I'm willing to spend the time to compile all my packages when there's an update. Phillip Smith wrote: > Hi all, > > I want to get everyone's input on the topic of Static vs. Dynamic > linking of packages. > > One of the problems I run in to at the moment on my mail server is > that I manually compile Postfix to take out MySQL and LDAP support > etc. The problem arises when the 'db' package is updated, which > Postfix is dynamically linked against. The db package gets upgraded, > then I have to go through the whole process of recompiling Postfix to > link against the new version. > > Given that we're aiming for stability in our package sets, should we > consider static linking of packages? > > Pros > - Packages don't need to be recompiled to link against upgrades in > other packages. > - Packages are more self-contained and less reliant on external packages. > > Cons > - Larger packages, in terms of byte size. Larger on-disk requirements > (Is this really an issue with the size of disks and price of GB these > days?) > - Packages don't get benefits of security or performance etc updates > in packages it relies on until the package is rebuilt. > > What is everyone's thoughts on this? > > Cheers, > ~p > _______________________________________________ > ArchServer Project General Mail List > Post messages to: general at lists.archserver.org > Administer your subscription: http://lists.archserver.org/listinfo/general >
