#23293: Deprecation & Deletion of Zope ports ------------------------------+-------------------------------- Reporter: charlie.clark@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: 1.8.2 Resolution: | Keywords: Port: zope zope-* | ------------------------------+-------------------------------- Comment (by petr@…): The deletion of zope ports was already proposed 5 years ago, and the zope ports were considered outdated at that time ("In the light of this and the extreme age"). From the ticket and a mail exchange on the devel list (https://lists.macosforge.org/pipermail/macports- dev/2014-July/027466.html) I understand that providing zope ports of recent versions is not useful any more. Currently, the following ports seem to be defect and probably it is not worth the effort to fix them as nobody uses them anyway: * #44421 zope-zphotoslides: fails to build * #44422 zope: fails to activate on lion buildbot * #44423 zope and zope-btreefolder2 conflict * #44424 zope-portaltransforms: fails to build * #44425 zope-externalfile: fails to patch * #44426 zope-cmfformcontroller: fails to build * #44428 zope-validation: build failure Other zope related tickets are the following: * #20773: Add zope2.10 * #43421: py-zopeinterface update to 4.1.1 and python 3.3+ support So can we proceed and delete the immediately without any deprecation period? There will be no update and no 'replaced_by', so probably this would be the easiest way to retire them all together. If you are okay with this I would proceed. -- Ticket URL: <https://trac.macports.org/ticket/23293#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X