[MacPorts] #44538: py-impressive: should be renamed and handled as an app
#44538: py-impressive: should be renamed and handled as an app --------------------+-------------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: py-impressive impressive --------------------+-------------------------------------- To my understanding impressive is an app and does not install modules. So it should be renamed to `impressive`. -- Ticket URL: <https://trac.macports.org/ticket/44538> MacPorts <http://www.macports.org/> Ports system for OS X
#44538: py-impressive: should be renamed and handled as an app ---------------------------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-impressive impressive | ---------------------------------------+-------------------------------- Comment (by mf2k@…): Go for it! You should {{{svn cp}}} py-impressive to impressive and change the name. Also use python 2.7 instead of 2.6. Then add a [https://trac.macports.org/wiki/PortfileRecipes#replaced-by obsolete stub port] for the old py-impressive portfile and say replaced_by impressive. -- Ticket URL: <https://trac.macports.org/ticket/44538#comment:1> MacPorts <http://www.macports.org/> Ports system for OS X
#44538: py-impressive: should be renamed and handled as an app ---------------------------------------+-------------------------------- Reporter: petr@… | Owner: macports-tickets@… Type: defect | Status: new Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-impressive impressive | ---------------------------------------+-------------------------------- Comment (by mf2k@…): See the port py-pygccxml-devel for an example of the obsolete portgroup and a python port. -- Ticket URL: <https://trac.macports.org/ticket/44538#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#44538: py-impressive: should be renamed and handled as an app ---------------------------------------+---------------------- Reporter: petr@… | Owner: petr@… Type: defect | Status: assigned Priority: Normal | Milestone: Component: ports | Version: Resolution: | Keywords: Port: py-impressive impressive | ---------------------------------------+---------------------- Changes (by petr@…): * owner: macports-tickets@… => petr@… * status: new => assigned Comment: Done in r123616. I do not adhere 100% to the example. The difference is that we do not `replace_by renamed subports here, right? -- Ticket URL: <https://trac.macports.org/ticket/44538#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
#44538: py-impressive: should be renamed and handled as an app ---------------------------------------+-------------------- Reporter: petr@… | Owner: petr@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-impressive impressive | ---------------------------------------+-------------------- Changes (by petr@…): * status: assigned => closed * resolution: => fixed -- Ticket URL: <https://trac.macports.org/ticket/44538#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
#44538: py-impressive: should be renamed and handled as an app ---------------------------------------+-------------------- Reporter: petr@… | Owner: petr@… Type: defect | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: fixed | Keywords: Port: py-impressive impressive | ---------------------------------------+-------------------- Comment (by mf2k@…): What you did looks good to me. -- Ticket URL: <https://trac.macports.org/ticket/44538#comment:5> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts