Hi,
I'm wondering what we should do for picking this. Do we go with bdb 4.7.25 with patches and whatever each distro provides for OpenSSL, GnuTLS etc. that we test on. Do we test various versions or just have some options in our initial build scripts to specify these? Do we pick versions we recommend for production or just something that will work for testing or do we only test an exact set of package versions with our build options?
I say we pick our versions with our build options and allow these to be set by either the person contributing the build box or us in the script. I think we can leave each distro to do the testing of the version of OpenLDAP they provide and whatever that distro uses as build reqs.
Thoughts?
Gavin.
ghenry@OpenLDAP.org wrote:
Hi,
I'm wondering what we should do for picking this. Do we go with bdb 4.7.25
with patches and whatever each distro provides for OpenSSL, GnuTLS etc. that we test on. Do we test various versions or just have some options in our initial build scripts to specify these? Do we pick versions we recommend for production or just something that will work for testing or do we only test an exact set of package versions with our build options?
I say we pick our versions with our build options and allow these to be set
by either the person contributing the build box or us in the script. I think we can leave each distro to do the testing of the version of OpenLDAP they provide and whatever that distro uses as build reqs.
Thoughts?
I think we pick a core set of packages that we control specifically, and leave the rest to whatever's on the platform. Currently that would include BerkeleyDB, OpenSSL, and Cyrus SASL. I occasionally run tests across BDB 4.4, 4.5, 4.6 and 4.7 but in general I don't think it's important to test more than the current 4.7.
The focus is obviously on finding portability issues in our own code. We have to assume that the other packages' teams already have a handle on their own portability issues.
--On Friday, April 10, 2009 1:32 PM -0700 Howard Chu hyc@symas.com wrote:
I think we pick a core set of packages that we control specifically, and leave the rest to whatever's on the platform. Currently that would include BerkeleyDB, OpenSSL, and Cyrus SASL. I occasionally run tests across BDB 4.4, 4.5, 4.6 and 4.7 but in general I don't think it's important to test more than the current 4.7.
The focus is obviously on finding portability issues in our own code. We have to assume that the other packages' teams already have a handle on their own portability issues.
What about Heimdal? libltdl? We've invariably hit problems with bad platform builds of libltdl at least.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration