#15372: octave-forge-2006.07.09 depends on port ginac but should be GiNaC -------------------------------+-------------------------------------------- Reporter: blb@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: port bug typo dependency -------------------------------+-------------------------------------------- Comment (by alakazam@melix.net): The {{{octave-forge}}} port has actually been deprecated in favor of individual portfiles for each {{{octave-forge}}} package. What is the preferred way to handle deprecated port files' removals ? -- Ticket URL: <http://trac.macports.org/ticket/15372#comment:1> MacPorts <http://www.macports.org/> Ports system for Mac OS

#15372: octave-forge-2006.07.09 depends on port ginac but should be GiNaC -------------------------------+-------------------------------------------- Reporter: blb@macports.org | Owner: macports-tickets@lists.macosforge.org Type: defect | Status: new Priority: Normal | Milestone: Port Bugs Component: ports | Version: 1.6.0 Resolution: | Keywords: port bug typo dependency -------------------------------+-------------------------------------------- Comment (by alakazam@melix.net): Ticket #15419 suggests deprecating {{{octave-forge}}} since [http://trac.macports.org/changeset/36910 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. This problem should probably be filed against the {{{octave}}} port itself, if it is present, the individual {{{octave-*}}} Portfiles shouldn't have this problem, as they only depend on the {{{octave}}} port. -- Ticket URL: <http://trac.macports.org/ticket/15372#comment:3> MacPorts <http://www.macports.org/> Ports system for Mac OS