[MacPorts] #37995: mapnik and py26-mapnik
#37995: mapnik and py26-mapnik --------------------------+-------------------------------- Reporter: ryandesign@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: mapnik py26-mapnik --------------------------+-------------------------------- What is the situation with mapnik and py26-mapnik? Why do both exist? mapnik appears to be current while py26-mapnik is vastly out of date and does not build and has several tickets filed against it and is no longer being maintained by its maintainer. Should py26-mapnik be replaced_by mapnik? -- Ticket URL: <https://trac.macports.org/ticket/37995> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37995: mapnik and py26-mapnik ---------------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mapnik py26-mapnik | ---------------------------------+------------------------ Comment (by stromnov@…): Yes, I think that py26-mapnik should be replaced by mapnik. And mapnik is a C++ GIS library with optional python bindings (and other plugins), so mapnik must be in gis/mapnik, but not in python/py*-mapnik. -- Ticket URL: <https://trac.macports.org/ticket/37995#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37995: mapnik and py26-mapnik ---------------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mapnik py26-mapnik | ---------------------------------+------------------------ Comment (by macports@…): There were pretty serious changes to the Mapnik API for version 2. Would "replaced_by" cause an automatic upgrade from Mapnik 0.7 (as in py26-mapnik) to Mapnik 2.1? -- Ticket URL: <https://trac.macports.org/ticket/37995#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37995: mapnik and py26-mapnik ---------------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mapnik py26-mapnik | ---------------------------------+------------------------ Comment (by ryandesign@…): Yes, that would be the purpose of adding that directive. If there is a reason why an older mapnik should be kept, then it should be renamed from py26-mapnik to mapnik07 or something. -- Ticket URL: <https://trac.macports.org/ticket/37995#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#37995: mapnik and py26-mapnik ---------------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mapnik py26-mapnik | ---------------------------------+------------------------ Comment (by petr@…): Could we get rid of the `py26-mapnik` code by now? It is quite dated now, and mapnik is around for some while. Not sure I understand the issue regarding `replaced_by mapnik`, why this should create any problems due to the API changes. Mapnik seems to have no dependents. The only issue I could think of is that `py26-mapnik` would correspond to mapnik +python26, while the default is +python27. So what would be a smooth exit strategy? -- Ticket URL: <https://trac.macports.org/ticket/37995#comment:6> MacPorts <http://www.macports.org/> Ports system for OS X
#37995: mapnik and py26-mapnik ---------------------------------+------------------------ Reporter: ryandesign@… | Owner: stromnov@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: mapnik py26-mapnik | ---------------------------------+------------------------ Comment (by petr@…): See also ticket #30187. -- Ticket URL: <https://trac.macports.org/ticket/37995#comment:7> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts