#13909 closed defect (fixed)
octave-forge should depend on gcc42 if possible
| Reported by: | brentn@… | Owned by: | macports-tickets@… |
|---|---|---|---|
| Priority: | Normal | Milestone: | |
| Component: | ports | Version: | 1.6.0 |
| Keywords: | Cc: | stechert@…, ryandesign (Ryan Carsten Schmidt) | |
| Port: |
Description
octave 2.9.15 has been updated to depend on gcc42. octave-forge hasn't, which leads to both compilers being installed if you do a clean install of octave-forge.
Change History (5)
comment:1 Changed 17 years ago by ryandesign (Ryan Carsten Schmidt)
| Cc: | stechert@… ryandesign@… added |
|---|
comment:2 Changed 17 years ago by brentn@…
It is certainly possibly and desirable in my opinion to merge the two into a single package. The binary distribution of Octave 3.0 has the octave-forge functionality packaged in, for instance. However, the port of 2.9.15 does not have any of the octave-forge packages built-in (e.g., boxplot, rankcorr.) Bottom line, #11987 might be possible in the future, but is not workable with the current octave port.
comment:3 Changed 16 years ago by alakazam@…
Ticket #15419 suggests deprecating octave-forge since Changeset 36910 ensures support of the various octave-forge packages with the octave-3.0 port.
I believe that this ticket can be closed, and filed again against the specific octave-* Portfiles that might exhibit this problem.
comment:4 Changed 16 years ago by alakazam@…
| Resolution: | → fixed |
|---|---|
| Status: | new → closed |
Perhaps, but #11987 says the octave-forge port should be deleted, because the functionality of octave-forge can now be achieved within octave. Do you disagree? (I don't know because I don't use octave.)