[MacPorts] #39386: port CUTEr
#39386: port CUTEr -------------------------+-------------------------------- Reporter: pengyu.ut@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Keywords: | Port: -------------------------+-------------------------------- [http://www.cuter.rl.ac.uk/index.html] -- Ticket URL: <https://trac.macports.org/ticket/39386> MacPorts <http://www.macports.org/> Ports system for OS X
#39386: port CUTEr --------------------------+-------------------------------- Reporter: pengyu.ut@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by jdgleeson@…): CUTEr has a successor, CUTEst, announced here: http://www.netlib.org/na- digest-html/13/v13n19.html#1 What do you think of porting CUTEst instead of CUTEr? -- Ticket URL: <https://trac.macports.org/ticket/39386#comment:2> MacPorts <http://www.macports.org/> Ports system for OS X
#39386: port CUTEr --------------------------+-------------------------------- Reporter: pengyu.ut@… | Owner: macports-tickets@… Type: request | Status: new Priority: Normal | Milestone: Component: ports | Version: 2.1.3 Resolution: | Keywords: Port: | --------------------------+-------------------------------- Comment (by pengyu.ut@…): Replying to [comment:2 jdgleeson@…]:
CUTEr has a successor, CUTEst, announced here: http://www.netlib.org/na- digest-html/13/v13n19.html#1
What do you think of porting CUTEst instead of CUTEr?
I just noticed this as well. Yes, CUTEst should be ported instead of CUTEr. [http://ccpforge.cse.rl.ac.uk/gf/project/cutest/] -- Ticket URL: <https://trac.macports.org/ticket/39386#comment:3> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts