On Thu, 6 Oct 2011, Matthijs Mekking wrote:
I don't fully grasp your problem: if unbound does not link against libunbound, upgrading the unbound package would not need to update the libunbound package.
But if a fix is applied to unbound-libs, the unbound daemon will still be using an old copy. Also, the results of unbound vs unbound-host could then be different. As a rule, it is always bad to have duplicatated staticly linked code from a dynamic library into any executable - it becomes unmanagable. To avoid this, I will make unbound depend on unbound-libs of the identical version so that we keep the daemon and libraries in sync with each other.
It is of course possible to use the library dynamically, but probably unbound links statically for performance optimization reasons.
Can you explain those to me? Paul _______________________________________________ Unbound-users mailing list [email protected] http://unbound.nlnetlabs.nl/mailman/listinfo/unbound-users
