Opened 12 years ago

Closed 7 years ago

#23293 closed defect (fixed)

Deprecation & Deletion of Zope ports

Reported by: Themanwithoutaplan Owned by: petrrr
Priority: Normal Milestone:
Component: ports Version: 1.8.2
Keywords: Cc: mww@…, MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Port: zope zope-*

Description

With the release of Zope 2.12 the Zope now uses the buildout framework for package installation with py-setuptools or py-distribute being the only dependency. In the light of this and the extreme age of many of the Zope ports I suggest that all zope-ports be removed from the tree.

I couldn't find any reference to port deletion or deprecation in the documentation.

Change History (9)

comment:1 Changed 12 years ago by jmroot (Joshua Root)

Cc: mww@… mcalhoun@… added
Type: requestdefect

comment:2 Changed 7 years ago by petrrr

Cc: petr@… added

Cc Me!

comment:3 Changed 7 years ago by petrrr

Keywords: zope removed
Port: zope zope-* added

comment:4 Changed 7 years ago by petrrr

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.

comment:5 Changed 7 years ago by Themanwithoutaplan

Most of those ports are not really part of Zope and are all outdated. Zope itself has been modular since 2.12 and comes with its own very reliable dependency and build management system. Zope 2.10 is no longer supported or maintained so this port should not be added.

py-zopeinterface might be worth interesting as it is a library that is reasonably widely used outside the Zope world. However, I suspect most people who need it will simply install it using pip or list it as a dependency.

I would be happy for you to proceed with removing these ports.

comment:6 Changed 7 years ago by petrrr

Okay for the moment I closed #20773 as wontfix.

comment:7 Changed 7 years ago by petrrr

In r126471 the defect ports as listed above are removed.

Waiting few more days before deleting the remaining zope-* ports and zope @2.8.7_2 itself. Port py-zopeinterface will not be deleted.

comment:8 Changed 7 years ago by petrrr

Cc: petr@… removed
Owner: changed from macports-tickets@… to petr@…
Status: newassigned

comment:9 Changed 7 years ago by petrrr

Resolution: fixed
Status: assignedclosed

r126913 removes all zope-* ports, r126914 removes port zope.

Note: See TracTickets for help on using tickets.