Opened 4 years ago

Closed 4 years ago

#50397 closed update (fixed)

octave-general @1.3.4_0: update to 2.0.0

Reported by: Schamschula (Marius Schamschula) Owned by: macports-tickets@…
Priority: Normal Milestone:
Component: ports Version: 2.3.4
Keywords: haspatch Cc: michaelld (Michael Dickens), MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)
Port: octave-general

Description

octave-general has been updated to version 2.0.0. New this version:

  • Package is now dependent on Octave version 4.0.0 to avoid conflicts with missing inputParser.
  • The @inputParser has been removed since it is now part of Octave core and has a completely Matlab compatible syntax. There may be issues for developers who will not know what inputParser class is being used by others. A workaround can be:
     p = inputParser ();
     f (strfind (which ("inputParser"), ["@inputParser" filesep "inputParser.m"]))
      ## @inputParser specific code (previous general package)
     else
      ## use Octave core inputParser implementation
     endif
    
  • The `cauchy' function is new on the general package. It has been moved from the optim package.

Attachments (1)

Portfile-octave-general.diff (785 bytes) - added by Schamschula (Marius Schamschula) 4 years ago.

Download all attachments as: .zip

Change History (6)

Changed 4 years ago by Schamschula (Marius Schamschula)

comment:1 Changed 4 years ago by michaelld (Michael Dickens)

Cc: michaelld@… added

Cc Me!

comment:2 Changed 4 years ago by michaelld (Michael Dickens)

I can't do this update until we move octave to the 4.0 series. Which, honestly, it's time for anyway. Hmmm ... do you feel comfortable doing the Portfile shuffle here for moving octave-devel to octave?

comment:3 Changed 4 years ago by Schamschula (Marius Schamschula)

I've been running some form of octave 4.0.x since last August.

I recently switched from rolling my own Portfile based on the legacy octave Portfile to using octave-devel-release (which is missing a patch and has an aesthetical issue with the GUI under OS X) to octave-devel-rc which has fixed this issue upstream.

Thus, I'm building active packages against the octave 4.0.1 release candidate. Of course octave-devel-rc is also already out of date with rc1 rather than rc3.

comment:4 Changed 4 years ago by MarcusCalhoun-Lopez (Marcus Calhoun-Lopez)

Cc: mcalhoun@… added

Cc Me!

comment:5 Changed 4 years ago by michaelld (Michael Dickens)

Resolution: fixed
Status: newclosed

Meh. Updating this anyway. Done in r145603.

Note: See TracTickets for help on using tickets.