[MacPorts] #31949: octave: new version of portgroup (octave 1.1)
#31949: octave: new version of portgroup (octave 1.1) --------------------------------+------------------------------------------- Reporter: nicos@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------------------+------------------------------------------- Some recent octave packages require to be compiled within octave, and not through standard tools. This updated version of the octave portgroup aims at enabling this type of installation, and should be compatible with both octave and octave-devel present versions. -- Ticket URL: <https://trac.macports.org/ticket/31949> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31949: octave: new version of portgroup (octave 1.1) --------------------------------+------------------------------------------- Reporter: nicos@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------------------+------------------------------------------- Changes (by macsforever2000@…): * cc: michaelld@… (added) Comment: Ccing the maintainer of octave-devel. Nicos: Since octave and the subports seem largely not maintained, why not commit this yourself? -- Ticket URL: <https://trac.macports.org/ticket/31949#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31949: octave: new version of portgroup (octave 1.1) --------------------------------+------------------------------------------- Reporter: nicos@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------------------+------------------------------------------- Comment(by nicos@…): I could do that, but as I am still slightly unexperienced as a macports maintainer, I was not sure that it would be a good idea to commit just like that portgroups without submitting as a ticket before, in order to ensure that there was not anything shocking in it. -- Ticket URL: <https://trac.macports.org/ticket/31949#comment:2> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31949: octave: new version of portgroup (octave 1.1) --------------------------------+------------------------------------------- Reporter: nicos@… | Owner: macports-tickets@… Type: enhancement | Status: new Priority: Normal | Milestone: Component: ports | Version: Keywords: | Port: --------------------------------+------------------------------------------- Comment(by michaelld@…): Adding a portgroup is OK (by me) -- folks don't have to use it if they don't want to, and/or they can fix it if it's broken. I haven't looked at what you did, but if it works with both octave and octave-deve, both in the traditional way as well as compiled with octave itself, then that's a sign you're on the right track. -- Ticket URL: <https://trac.macports.org/ticket/31949#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS
#31949: octave: new version of portgroup (octave 1.1) --------------------------+-------------------------------- Reporter: nicos@… | Owner: macports-tickets@… Type: enhancement | Status: closed Priority: Normal | Milestone: Component: ports | Version: Resolution: invalid | Keywords: Port: | --------------------------+-------------------------------- Changes (by michaelld@…): * status: new => closed * resolution: => invalid Comment: I pushed a new PortGroup for octave-1.0 in r114034. Maybe I should have gone to 1.1, but 1.0 was so broken that it made more sense replacing it. Too late now ... -- Ticket URL: <https://trac.macports.org/ticket/31949#comment:4> MacPorts <http://www.macports.org/> Ports system for OS X
participants (1)
-
MacPorts