Hello Daryl, On Wed, Oct 31, 2012 at 9:48 PM, Daryl Herzmann <akrh...@gmail.com> wrote: > Howdy, > > I built basemap 1.0.5 and matplotlib 1.2.0rc3 via the simple command 'python > setup.py bdist_rpm' without an error that I can tell. When I attempt to > install them, I get a conflict between the two. For example: > > file /usr/lib64/python2.6/site-packages/mpl_toolkits/__init__.pyc from > install of basemap-1.0.5-1.x86_64 conflicts with file from package > matplotlib-1.2.0rc3-1.x86_64 > file /usr/lib64/python2.6/site-packages/mpl_toolkits/__init__.pyo from > install of basemap-1.0.5-1.x86_64 conflicts with file from package > matplotlib-1.2.0rc3-1.x86_64 > > Working around this error is easy with some rpm flags, but was curious what > the proper solution for this situation is?
In Debian we're dealing with this situation letting 'matplotlib' package owning the "mpl_toolkits" namespace (so only matplotlib will install the __init__.py file in that directory) and basemap will install stuff in "mpl_toolkits/basemap" directory and depending on matplotlib (it requires to NOT install mpl_toolkits/__init__.py file when install basemap, by either remote it when creating the package or similar solution). This way matplotlib package will create the namespace for all the other packages to install modules in it, and avoiding conflicts like the one you described. HTH, -- Sandro Tosi (aka morph, morpheus, matrixhasu) My website: http://matrixhasu.altervista.org/ Me at Debian: http://wiki.debian.org/SandroTosi ------------------------------------------------------------------------------ Everyone hates slow websites. So do we. Make your web apps faster with AppDynamics Download AppDynamics Lite for free today: http://p.sf.net/sfu/appdyn_sfd2d_oct _______________________________________________ Matplotlib-users mailing list Matplotlib-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/matplotlib-users
