[omniORB] omniORBpy: __init__.py installed in site-packages
Floris Bruynooghe
flub at devork.be
Sun Jun 5 21:19:00 BST 2011
Hi
It seems that __init__.py gets installed in the toplevel
site-packages. While generally not very harmful I'm sure it can
hardly be deemed as correct. The offending code seems to be in
python/COS/dir.mk, here a small patch which fixes this:
--- a/python/COS/dir.mk
+++ b/python/COS/dir.mk
@@ -78,8 +78,8 @@
EXPORTEDFILES += $(foreach f, $(filter CosNaming%, $(FILES)),
$(PYLIBROOT)/$(f))
# __init__.py to make it a package
-FILES += __init__.py
-INSTALLEDFILES += $(INSTALLPYTHONDIR)/__init__.py
+#FILES += __init__.py
+#INSTALLEDFILES += $(INSTALLPYTHONDIR)/__init__.py
# A .pth file to expose omniORB/COS to the global namespace
FILES += omniORB.pth
I'm not sure why that was there, am I disabling something important by
this change?
Regards
Floris
--
Debian GNU/Linux -- The Power of Freedom
www.debian.org | www.gnu.org | www.kernel.org
More information about the omniORB-list
mailing list