#27397: New port: py26-scientific-devel --------------------------------------------+------------------------------- Reporter: danmichaelo+macports@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: py26-scientific-devel --------------------------------------------+------------------------------- Changes (by ryandesign@…): * cc: adfernandes, akitada (removed) * cc: adfernandes@…, akitada@… (added) * port: => py26-scientific-devel Old description:

My portfile is based on the portfile for py26-scientific. I modified the build.cmd to use numpy instead of numeric {{{ build.cmd ${python.bin} setup.py --numpy --no-user-cfg }}} Some ports depends on py26-scientific, for example py26-ipython and py26-MMTK. I do not now how to let these use py26-scientific-devel instead of py26-ipython. I hope some more experienced macports contributors can comment on this.

New description: My portfile is based on the portfile for py26-scientific. I modified the build.cmd to use numpy instead of numeric {{{ build.cmd ${python.bin} setup.py --numpy --no-user-cfg }}} Some ports depends on py26-scientific, for example py26-ipython and py26-MMTK. I do not now how to let these use py26-scientific-devel instead of py26-scientific. I hope some more experienced macports contributors can comment on this. -- Comment: Why do we need a devel version of this port? -- Ticket URL: <https://trac.macports.org/ticket/27397#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS

#27397: New port: py26-scientific-devel --------------------------------------------+------------------------------- Reporter: danmichaelo+macports@… | Owner: macports-tickets@… Type: submission | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: haspatch | Port: py26-scientific-devel --------------------------------------------+------------------------------- Comment(by adfernandes@…): Hmm... someone might want to write a note to the ScientificPython people and let them know that their version numbering is causing problems for package maintainers. As a busy academic, I really understand the time and effort constraints that they likely are working on. However, the "official" and "unofficial" versioning that they are using really messes things up. Can you verify that moving from ScientificPython 2.8 to 2.9 is '''forward''' compatible? If so, I can update the port to the newest version. -- Ticket URL: <https://trac.macports.org/ticket/27397#comment:4> MacPorts <http://www.macports.org/> Ports system for Mac OS