https://bugzilla.redhat.com/show_bug.cgi?id=835432 --- Comment #6 from John Morris <john@xxxxxxxxxxx> --- (In reply to comment #1) > Just out of the top of my head it feels that the source files in /usr/share > might be better off under /include in this case, something like > /usr/include/cxx/src. After all, these sources are indeed development files. > One path less to track... but it's really a special case. Yeah, /usr/include/cxx/src is a good idea, and something does need to be done about it. Putting files in /usr/share/python2.7/cxx violates the Pkging Guidelines because no package owns /usr/share/python2.7, and it doesn't make sense for python-pycxx to own that directory. Maybe this needs to be taken up with upstream. I'd think these ought to be compiled for the arch and put into a static lib like %{_libdir}/pycxx.a. Another option is to put the uncompiled sources in /usr/src/pycxx, but I haven't found a precedent for that, outside of the kernel (PlanetCCRMA does this with rt-tests, but I haven't investigated). A complaint I have about headers in /usr/include/python2.7 is that these include files should be good for any python v.2. That may not matter if the python minor version is guaranteed not to change within any Fedora release. -- You are receiving this mail because: You are on the CC list for the bug. _______________________________________________ package-review mailing list package-review@xxxxxxxxxxxxxxxxxxxxxxx https://admin.fedoraproject.org/mailman/listinfo/package-review