Bug 450692
Summary: | [pyuno] pyuno should be in default PYTHONPATH | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Alex Lancaster <alex> |
Component: | openoffice.org | Assignee: | Caolan McNamara <caolanm> |
Status: | CLOSED CANTFIX | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | low | Docs Contact: | |
Priority: | low | ||
Version: | rawhide | CC: | jnavrati |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2008-06-13 12:17:19 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 438527 |
Description
Alex Lancaster
2008-06-10 13:49:37 UTC
debian pulls this off by a rpath to %{_libdir}/openoffice.org/program which our guidelines (http://fedoraproject.org/wiki/Packaging/Guidelines#Beware_of_Rpath) doesn't allow what about... "import uno" rather than directly "import pyuno" which imports pyuno with sufficient magic to make it work That might be better, but it still means that 3rd-party packages (bibus in this case) will still have special-case for Fedora, since other distros will assume that the module should be able to be imported directly and won't see a need to check for that module name. Which brings us back to the original problem. Is there any reason why OOo can't install it in the usual place and look for it there? I know it's very tied to OOo, but it is a Python module, after all. I suspect that "import uno" will also works on debian et. al. If it did, that'd be ideal. pyuno.so does a dlopen(libpyuno.so). So if pyuno.so is moved into the python lib dir then libpyuno.so must either be moved in there as well, and if that's moved in there then the global linker or python path has to extended to /usr/lib/openoffice.org because libpyuno.so links against a stack of stuff in that dir, both options are sort of horrific. Like I said, the debian workaround is probably the patch I see in ooo-build of... + @echo $(LINK) -Wl,-z,combreloc $(LINKFLAGS) $(LINKFLAGSRUNPATH_OOO) -Wl,-rpath,/usr/lib/openoffice/program $(LINKFLAGSSHLCUI) -ldl -o $@ $(SLO)$/pyuno_dlopenwrapper.o > $(MISC)$/$(@:b).cmd which isn't acceptable by http://fedoraproject.org/wiki/Packaging/Guidelines#Beware_of_Rpath well "import uno" will work, and I think will work on all systems, and bring in pyuno so that might be a suitable global upstream solution. If someone can figure out a way to place pyuno in the right place to allow "import pyuno" to work without violating the rpath guidelines then I'm all for it. Maybe when the dust has settled on the 3 layer OOo it might be possible to see a route towards placing the ure libs in standard /usr/lib path, and that might work. But I'm not sure that it would be sufficient If "import uno" works at the moment in actual release, then this should be closed. But if it doesn't yet work, then it should be kept open. I'm not sure why it should be closed CANTFIX, at the least, it could be closed as UPSTREAM, since it might be fixed there. This definitely doesn't work on F-8: $ python Python 2.5.1 (r251:54863, Oct 30 2007, 13:54:11) [GCC 4.1.2 20070925 (Red Hat 4.1.2-33)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import uno Traceback (most recent call last): File "<stdin>", line 1, in <module> ImportError: No module named uno but it does on F-9: $ python Python 2.5.1 (r251:54863, Apr 8 2008, 01:19:33) [GCC 4.3.0 20080404 (Red Hat 4.3.0-6)] on linux2 Type "help", "copyright", "credits" or "license" for more information. >>> import uno >>> uno (all with most recent updates) |