Fink

changed that and committed.

I got the following after I cleaned my system again and installed from the
.deb:

$ mayavi2
Traceback (most recent call last):
File "/sw/bin/mayavi2", line 5, in <module>
from pkg_resources import load_entry_point
ImportError: No module named pkg_resources

Looks like setuptools-py25 is needed at runtime.

I have updated the info file to the latest upstream version. It still
depends on the old vtk-py becuase "import vtk" fails from a Fink Python
session using the vtk52 and vtk54 packages.

It would definitely be better to use a more recent VTK. I didn't realize
that that the vtk52 package provided Python bindings. I will update and
test the package this weekend but I don't anticipate any problems. There is
also a new upstream release so I may update the version and submit updates
for Mayavi and its requirement ETS packages at the same time.

jedfrechette will be maintainer, I hope. I'll stay with the old mayavi
until it gets buried.

Thanks. Who gets to be maintainer?

This package looks good to me, with perhaps one exception: Would it compile
also with a more recent version of vtk (5.2 or 5.4) instead of vtk-py25,
which is vtk-5.0?

One advantage would be that the vtk52 (and now vtk54) packages have
-shlibs splitoffs that can coexist, whereas vtk-py25 is monolithic.
Currently, when I want to install vtk52 or vtk52, I have to remove mayavi2,
because it depends (not only builddepends) on vtk-py25 which in turn
conflicts with vtk52 (and vtk54).

For the time being, I would leave the old mayavi package in place, but I
would phase it out eventually (just like the older vtk packages, once I
manage to package a more recent version of netgen).

I don't have a strong opinion about how this package should be handled. It
can coexist with the existing Mayavi package (e.g. Debian has both Mayavi
and Mayavi2 packages). On the other hand, it is my understanding that with
this release all of Mayavi1's functionality is available in Mayavi2 so
maybe it would be better replace Mayavi1, which is no longer being
developed. I have never used Mayavi1 so I can't comment on what migrating
to Mayavi2 involves and I have no idea how many Mayavi1 users Fink may
have.

Martin: If the tracker hasn't contacted you yet, I think this is in your
territory.

I'm going to go ahead and assign this provisionally to Martin Costabel, the
maintainer of the current mayavi. I don't want to step on any toes here.

It might be worth checking with the maintainer of the existing mayavi
package.