Opened 10 years ago

Closed 9 years ago

#27397 closed submission (fixed)

New port: py26-scientific-devel

Reported by: danmichaelo+macports@… Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version:
Keywords: haspatch Cc: adfernandes (Andrew Fernandes), akitada@…
Port: py26-scientific-devel

Description (last modified by ryandesign (Ryan Schmidt))

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} --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.

Attachments (2)

Portfile (2.2 KB) - added by danmichaelo+macports@… 10 years ago.
files.tar.gz (1010 bytes) - added by danmichaelo+macports@… 10 years ago.

Download all attachments as: .zip

Change History (7)

Changed 10 years ago by danmichaelo+macports@…

Attachment: Portfile added

Changed 10 years ago by danmichaelo+macports@…

Attachment: files.tar.gz added

comment:1 Changed 10 years ago by danmichaelo+macports@…

Whoops, a typo slid in. I meant “instead of py26-scientific”, not “instead of py26-ipython”.

comment:2 Changed 10 years ago by ryandesign (Ryan Schmidt)

Cc: adfernandes@… akitada@… added; adfernandes akitada removed
Description: modified (diff)
Port: py26-scientific-devel added

Why do we need a devel version of this port?

comment:3 Changed 10 years ago by danmichaelo+macports@…

Hi. I'm not sure that we do, but I can explain why I added it. The stable version (2.8) is about two years old, while the unstable version (2.9) is only a few months newer. Since the unstable version is so old, it seems unlikely that a new stable version is right around the corner. Yet, 2.9 has introduced some new features that e.g. the package nMOLDYN (which is not yet on MacPorts) depends on. So I had to install it myself, and thought I could make a port for it in the process.

Btw., are there any guidelines for what to do with development versions in general?

comment:4 Changed 10 years ago by adfernandes (Andrew Fernandes)

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.

comment:5 Changed 9 years ago by jmroot (Joshua Root)

Resolution: fixed
Status: newclosed
Note: See TracTickets for help on using tickets.