Description of problem: The header files are installed twice by mongodb-devel, once in /usr/include/mongo (which is correct), and once without the mongo subdirectory. For example there are both of the following files: /usr/include/mongo/client/dbclient.h /usr/include/client/dbclient.h Only the latter should exist. This is troublesome in two ways: first you can easily produce code incompatible with say Debian (because "#include <client/dbclient.h>" works on Fedora, but will fail on Debian). For another very genericly named files (e.g. /usr/include/utils/array.h) are installed. Version-Release number of selected component (if applicable): # rpm -q mongodb-devel mongodb-devel-2.2.0-6.fc17.x86_64 How reproducible: Always Steps to Reproduce: 1. ls /usr/include/client 2. ls /usr/include/mongo/client Actual results: Both produce (the same) output. Expected results: Onl the latter should produce output. Additional info: I think there is a problem with scons, I didn't see anything atypical in the spec file (though scons options like "extrapath" make me suspicious). So if no proper fix can be found, removing the files after installing and packaging only %{_includedir}/mongo/ sounds reasonable to me.
Interesting, I wonder why that started happening. You are correct, in 2.0.7-2 everything is in just /usr/include/mongo/ and then for some reason it's duplicated in /usr/include/ Nathaniel, unless you can think of some reason we need it in both places, I'll see about working up an updated mongodb 2.2.2 that fixes this problem.
Sorry for the delay. I have verified that there isn't any extra files in /usr/include/ that aren't in /usr/include/mongo/ So it is safe to remove everything in /usr/include/ that isn't in the directory /usr/include/mongo/ I have also tried to find the problem in the scons config files. I do not feel comfortable with anything I found. So I will do it the simple way and remove the files in the spec file after they are installed. Expect a fix by the end of the day today.
mongodb-2.2.2-2.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/mongodb-2.2.2-2.fc18
Package mongodb-2.2.2-2.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing mongodb-2.2.2-2.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-0520/mongodb-2.2.2-2.fc18 then log in and leave karma (feedback).
mongodb-2.2.2-2.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.