Hello,
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
Thanks Meike
Meike Stone wrote:
Hello,
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
We can't answer this since there is no "the openldap rpm/deb package". The OpenLDAP Project distributes source code, not binary packages. What you can or can't do with a particular distro's binary package is a question you should ask of your distro/package provider.
2013/6/6 Howard Chu hyc@symas.com:
Meike Stone wrote:
Hello,
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
We can't answer this since there is no "the openldap rpm/deb package". The OpenLDAP Project distributes source code, not binary packages. What you can or can't do with a particular distro's binary package is a question you should ask of your distro/package provider.
I mean, I have installed the normal (latest) openldap package. After them, I download the source tarball from OpenLDAP and want only use the tests to check the installation. How can in invoke the test separately from the unpacked tarball?
Thanks Meike
В Чтв, 06/06/2013 в 06:13 -0700, Howard Chu пишет:
Meike Stone wrote:
Hello,
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
We can't answer this since there is no "the openldap rpm/deb package". The OpenLDAP Project distributes source code, not binary packages. What you can or can't do with a particular distro's binary package is a question you should ask of your distro/package provider.
Most distributions provide source packages which can be build inplace with same options that the binary one have and one can run tests there.
Meike Stone writes:
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
No. tests/progs/ in the test suite uses libraries and generated include files which are not installed, they're only used for building OpenLDAP.
Hello,
thanks for answer, that a great pity!
Meike
2013/6/6 Hallvard Breien Furuseth h.b.furuseth@usit.uio.no:
Meike Stone writes:
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
No. tests/progs/ in the test suite uses libraries and generated include files which are not installed, they're only used for building OpenLDAP.
-- Hallvard
On 06/06/2013 03:58 PM, Meike Stone wrote:
Hello,
thanks for answer, that a great pity!
If your purpose is to test the distribution's builds, you can surely download the corresponding OpenLDAP source code, build it, replace slapd and slap* tools in BUILDDIR/servers/slapd with those provided by the distribution, and run the tests using "make test" or "cd tests; ./run testXXX" where XXX is the number of the test you need.
p.
Meike
2013/6/6 Hallvard Breien Furuseth h.b.furuseth@usit.uio.no:
Meike Stone writes:
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
No. tests/progs/ in the test suite uses libraries and generated include files which are not installed, they're only used for building OpenLDAP.
-- Hallvard
If your purpose is to test the distribution's builds,
Yes, that's is my intention.
you can surely download the corresponding OpenLDAP source code, build it, replace slapd and slap* tools in BUILDDIR/servers/slapd with those provided by the distribution, and run the tests using "make test" or "cd tests; ./run testXXX" where XXX is the number of the test you need.
Ahh, that sounds great, I'll check that!
Thanks to all,
Meike
Meike Stone wrote:
If your purpose is to test the distribution's builds,
Yes, that's is my intention.
you can surely download the corresponding OpenLDAP source code, build it, replace slapd and slap* tools in BUILDDIR/servers/slapd with those provided by the distribution, and run the tests using "make test" or "cd tests; ./run testXXX" where XXX is the number of the test you need.
Ahh, that sounds great, I'll check that!
As I note in my previous email, it's not as simple as that, unless you build your source tree with exactly the same configure options as the package you want to test against.
On 06/06/2013 06:02 PM, Howard Chu wrote:
Meike Stone wrote:
If your purpose is to test the distribution's builds,
Yes, that's is my intention.
you can surely download the corresponding OpenLDAP source code, build it, replace slapd and slap* tools in BUILDDIR/servers/slapd with those provided by the distribution, and run the tests using "make test" or "cd tests; ./run testXXX" where XXX is the number of the test you need.
Ahh, that sounds great, I'll check that!
As I note in my previous email, it's not as simple as that, unless you build your source tree with exactly the same configure options as the package you want to test against.
Right, but for most of the tests (especially if cherry-picked) it should work. On a related note, in tests/scripts/defines.sh we define
SLAPD="$TESTWD/../servers/slapd/slapd -s0" LDAPPASSWD="$CLIENTDIR/ldappasswd $TOOLARGS" LDAPSASLSEARCH="$CLIENTDIR/ldapsearch $TOOLPROTO $LDAP_TOOLARGS -LLL" LDAPSEARCH="$CLIENTDIR/ldapsearch $TOOLPROTO $TOOLARGS -LLL" LDAPRSEARCH="$CLIENTDIR/ldapsearch $TOOLPROTO $TOOLARGS" LDAPDELETE="$CLIENTDIR/ldapdelete $TOOLPROTO $TOOLARGS" LDAPMODIFY="$CLIENTDIR/ldapmodify $TOOLPROTO $TOOLARGS" LDAPADD="$CLIENTDIR/ldapmodify -a $TOOLPROTO $TOOLARGS" LDAPMODRDN="$CLIENTDIR/ldapmodrdn $TOOLPROTO $TOOLARGS" LDAPWHOAMI="$CLIENTDIR/ldapwhoami $TOOLARGS" LDAPCOMPARE="$CLIENTDIR/ldapcompare $TOOLARGS" LDAPEXOP="$CLIENTDIR/ldapexop $TOOLARGS"
by hacking those macros one could avoid copying or creating symlinks.
p.
Meike Stone wrote:
Hello,
thanks for answer, that a great pity!
Meike
2013/6/6 Hallvard Breien Furuseth h.b.furuseth@usit.uio.no:
Meike Stone writes:
is it possible and how, to run the complete test suite included in the source tarball later, after installing the openldap rpm/deb package independently and separated from the compilation?
No. tests/progs/ in the test suite uses libraries and generated include files which are not installed, they're only used for building OpenLDAP.
Well. The tools in tests/progs are only used in a handful of the tests (008, 039, 060, maybe a couple other back-ldap/back-meta tests) and you could of course compile them in the source tree and use them against the packaged binaries. Or just skip the tests that use them.
But the bigger problem is the configuration that's needed to make the test scripts work with an installed package. I.e., tests/run.in needs to be converted to tests/run and tweaking that manually would be quite a chore. Also tests/scripts/defines.sh assumes a lot of the binaries are present in the source tree; you'd either have to override the paths in the script or create symlinks in the source tree to point to the corresponding binaries.
It could all be done, certainly, if you have the patience.
openldap-technical@openldap.org