Previous to my last Linux build, I've always built OpenLdap from source. My latest build has pre-compiled OpenLdap and rather than rebuild everything, is there a way to easily figure out what options were used to create this build?
Thank you for your time in looking at this issue.
Mark Molenda
EDS Consulting Services
Integration Soa Services http://www.consultingservices.us.eds.com/nlapps/docs/default.asp?fid=41 7
--On Friday, April 25, 2008 10:20 AM -0400 "Molenda, Mark P" mark.molenda@eds.com wrote:
Previous to my last Linux build, I've always built OpenLdap from source. My latest build has pre-compiled OpenLdap and rather than rebuild everything, is there a way to easily figure out what options were used to create this build?
Contact your linux distributor. The OpenLDAP project provides source only.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
It was Novell's Suse Enterprise Server 10 sp1. If there is no way I would think that a future feature would be to save off those items that are requested in the build, even for folks taking over a system built a couple of years ago, it is probably unreasonable to have a production system rebuilt just to verify everything you need is in there. Or maybe a subset of the very good extensive tests that are part of the check when doing a source build could be pulled out and used to verify the feature set of the existing build. Being in the commercial end for awhile documentation is sometimes rare and verification would be very nice. Maybe store it in an entry in a special part of the schema....
Something to think about anyway. Thank you for your reply. -Mark
-----Original Message----- From: Quanah Gibson-Mount [mailto:quanah@zimbra.com] Sent: Monday, April 28, 2008 4:43 PM To: Molenda, Mark P; openldap-technical@openldap.org Subject: Re: Features supported
--On Friday, April 25, 2008 10:20 AM -0400 "Molenda, Mark P" mark.molenda@eds.com wrote:
Previous to my last Linux build, I've always built OpenLdap from source. My latest build has pre-compiled OpenLdap and rather than rebuild everything, is there a way to easily figure out what options
were
used to create this build?
Contact your linux distributor. The OpenLDAP project provides source only.
--Quanah
--
Quanah Gibson-Mount Principal Software Engineer Zimbra, Inc -------------------- Zimbra :: the leader in open source messaging and collaboration
On Monday 28 April 2008 22:50:23 Molenda, Mark P wrote:
It was Novell's Suse Enterprise Server 10 sp1.
Then, try and locate the source rpm that the binaries were built from. For example, 'rpm -qi openldap2' or similar would tell you the exact name of the source rpm. You should be able to download or request this source rpm from SUSE.
For example, you can find the SRPM for the package of current OpenLDAP 2.3 provided at the OpenSUSE build service for SLE10 here:
http://download.opensuse.org/repositories/OpenLDAP/SLE_10/src/
A brief look at those packages seems to indicate that most backends and overlays are built in statically, with just back-perl and back-meta as modules (in separate packages), based on which man pages were shipped in the openldap2 package ...
Anyway, please note that you should really know how to determine these details for any software you run, based on the methods used by your OS vendor ... and further discussion of SUSE specifics would probably be a bit off-topic.
Regards, Buchan
On Montag, 28. April 2008, Molenda, Mark P wrote:
It was Novell's Suse Enterprise Server 10 sp1.
Our packages are currently build with the following options: --enable-wrappers --enable-aclgroups --enable-spasswd --enable-modules \ --enable-shared --enable-dynamic --with-tls --with-cyrus-sasl \ --enable-crypt --enable-ipv6=yes --enable-aci --enable-bdb \ --enable-hdb --enable-ldbm --enable-rewrite --enable-ldap=yes \ --enable-meta=mod --enable-monitor=yes --enable-perl=mod \ --enable-slp --enable-overlays=yes --enable-lmpasswd
If there is no way I would think that a future feature would be to save off those items that are requested in the build,
The you should consider requesting that feature via the ITS. I agree that it could be useful.
Super thank you.
-----Original Message----- From: Ralf Haferkamp [mailto:rhafer@suse.de] Sent: Tuesday, April 29, 2008 3:43 AM To: openldap-technical@openldap.org Cc: Molenda, Mark P Subject: Re: Features supported
On Montag, 28. April 2008, Molenda, Mark P wrote:
It was Novell's Suse Enterprise Server 10 sp1.
Our packages are currently build with the following options: --enable-wrappers --enable-aclgroups --enable-spasswd --enable-modules \ --enable-shared --enable-dynamic --with-tls --with-cyrus-sasl \ --enable-crypt --enable-ipv6=yes --enable-aci --enable-bdb \ --enable-hdb --enable-ldbm --enable-rewrite --enable-ldap=yes \ --enable-meta=mod --enable-monitor=yes --enable-perl=mod \ --enable-slp --enable-overlays=yes --enable-lmpasswd
If there is no way I would think that a future feature would be to save off those items that are requested in the build,
The you should consider requesting that feature via the ITS. I agree that it could be useful.
openldap-technical@openldap.org
-
Buchan Milne -
Molenda, Mark P -
Quanah Gibson-Mount -
Ralf Haferkamp