emerge =app-misc/gramps-3.0.0 QA Notice: Precompiled python object files do not belong in /usr/share /usr/share/gramps/ProgressDialog.pyo /usr/share/gramps/PlaceUtils.pyo /usr/share/gramps/UndoHistory.pyo ... I don't really know why this warning is here, I thought that a package could have python modules in it's pkgdir, even compiled. But if this is the police for python object files, then gramps need a patch.
Just leave the cc field alone, even if you know where to assign it. This is due to python-updater I think, as it searches /usr/lib/python-<old>/ for packages to be remegerged. So this is a bug. Will have a look later or tomorrow.
Haven't got to it, though I tried some things, still have to dig into the Makefiles. Anyway, will be away for some weeks now, so don't expect too much activity here.
After some time of succesless trying, I can tell: It is not a simple task. Modifying --datadir only affect some files, moving them manually around breaks "hard" (on configure) coded paths in the executables. Python team: Is /usr/lib/pythonxx/site-packages/ something canonical on which I can point my finger on so Gramps upstream has to move? Or is there any sane/good way to make the py{c,o} files visible in the path where python-update can see it?
Ok, I contacted upstream. Let's see what their answer is.
Created attachment 153103 [details, diff] gramps-3.0.0-pycompile.patch Here is a patch to fix byte compilation of python modules. It's untested. Please test back and report :)
> It's untested. Please test back and report :) ahh.. test and report back :)
Works just fine. Thank you very much!
Verified in portage, the patch solves the issue. Thanks for the fix.
