[MacPorts] #36919: ds9: new port for astronomical imaging and visualization application

[MacPorts]

#36919: ds9: new port for astronomical imaging and visualization application
------------------------+--------------------------------
 Reporter:  aronnax@…   |      Owner:  macports-tickets@…
     Type:  submission  |     Status:  new
 Priority:  Normal      |  Milestone:
Component:  ports       |    Version:  2.1.2
 Keywords:              |       Port:  ds9
------------------------+--------------------------------
 The attached patch adds a new port for DS9, an astronomical imaging and
 visualization application. I would like to solicit comments on this
 Portfile before I commit.

 DS9's source distribution builds, in addition to its own source, a number
 of third-party libraries, and then compresses everything into a zip
 archive. This zip archive is extracted into memory on the fly when the
 user launches DS9. So the port installs only two files, in the end:

  * ${prefix}/bin/ds9
  * ${prefix}/bin/ds9.zip (yeah, I know; this doesn't conform to the FHS,
 but ds9.zip is supposed to be in the same directory as ds9.)

 DS9 includes the following software, among others:
  * StarLink AST (port needed)
  * blt (port exists, but needs to be updated)
  * funtools (port exists, but needs to be updated)
  * TkHtml (port needed)
  * tclxml (port exists)
  * tkmpeg (port needed)
  * tcl (port exists)
  * tk (port exists)
  * tktable (port exists)
  * wcssubs (port needed)
  * xpa (port exists, needs to be upgraded)
  * zip (port exists)
  * zlib (port exists)

 The Debian package <http://packages.debian.org/wheezy/saods9> is
 substantially more fine-grained; it doesn't use the ds9.zip mechanism and
 it has the bundled software split up into different packages that are
 dependencies. The developer agrees that this is the correct approach.

 I could commit this port as it is, and then slowly gut the ds9.zip file as
 ports for the dependencies appear. Or, I could wait until all the
 dependencies are available and up to date, and only then commit a port
 that is structured like the Debian package. Or, if there is anyone on the
 list who happens to be an astronomer and has more experience with ds9 then
 me and understands its dependency tree better, I would be happy to hand
 this port to them.

 Thoughts?

-- 
Ticket URL: <https://trac.macports.org/ticket/36919>
MacPorts <http://www.macports.org/>
Ports system for Mac OS