Opened 13 years ago
Closed 11 years ago
#31949 closed enhancement (invalid)
octave: new version of portgroup (octave 1.1)
| Reported by: | NicosPavlov | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | |
| Keywords: | Cc: | michaelld (Michael Dickens) | |
| Port: |
Description
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.
Attachments (1)
Change History (5)
Changed 13 years ago by NicosPavlov
| Attachment: | octave-1.1.tcl added |
|---|
comment:1 Changed 13 years ago by mf2k (Frank Schima)
| Cc: | michaelld@… added |
|---|
comment:2 Changed 13 years ago by NicosPavlov
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.
comment:3 Changed 13 years ago by michaelld (Michael Dickens)
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.
comment:4 Changed 11 years ago by michaelld (Michael Dickens)
| Resolution: | → invalid |
|---|---|
| Status: | new → closed |
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 ...
Ccing the maintainer of octave-devel.
Nicos: Since octave and the subports seem largely not maintained, why not commit this yourself?