update vs new enthought ports

[Ryan Schmidt]

On Jul 6, 2011, at 10:15, Jonathan Stickel wrote:

> The enthought python packages have been recently updated with a major version increment (to 4.0.0).  I am planning to submit patches to the tracker to update the ports (at least the ones needed for mayavi). However, some of the packages have been consolidated and renamed.  For example, it appears that envisagecore and envisageplugins have been merged to just "envisage".  To avoid confusion and breaking dependencies for the existing enthought ports, I think newly named ports should be created.

Confusion should be avoided by correctly using the replaced_by keyword on ports that have been replaced by or merged into others.

Broken dependencies should be avoided by identifying all the ports currently depending on the replaced ports, and updating them.

The only reason to create new ports, rather than updating the exist ports, is if there is some incompatible change in the new versions -- some reason why users would still want to use the old versions.