Re: How to install Octave 4.0.1 on OS X Yosemite

[Ben Abbott]

> On Apr 16, 2016, at 5:29 AM, Sebastian Schöps <address@hidden> wrote:
> 
> Dear all, 
> 
> there is an extensive description here how to compile Octave via homebrew
> and how to make and distribute the binary as DMG:
> 
> http://wiki.octave.org/Create_a_MacOS_X_App_Bundle_Using_Homebrew
> 
> IMHO the advantages of Homebrew are that it tries to minimize the
> replication of libraries (the old octave binary based on macports was huge),
> the community is very friendly and it is developed by scientists for
> scientists. 
> 
> Sadly, the feedback from the Octave community for creating a Octave binary
> was not very enthusiastic. I posted a beta but I did not get much feedback
> (some of you may recall). Actually we had recently a sponsor who wanted to
> pay for the binary but nobody wanted to take the money. So, finally, I
> stopped working on the octave wikie page and binary. I am still maintaining
> the homebrew formula (4.0.1 is almost ready) and I am using the octave mac
> binary only internally at my university.
> 
> We could make a new attempt to update the wiki page and create a binary
> release but then I need to be sure that I get some help.
> 
> Bye
> Sebastian

Hi Sabastian,

I put in most of the effort for the macports based bundle. The macports 
approach had the potential of being easily automated and maintained. But most 
important to me, the result was a self contained app-bundle (i.e. if you 
CMD-Delete the application, everything is gone … with nothing left behind in 
/usr/local or some other location).

The large size was ultimately due to three “features”.
(1) The build tools were included to ensure that packages would be built with a 
compatible tool chain.
(2) A complete TeX distribution was included since that was only macports 
supported method to include TeXinfo (needed for the help command).
(3) X11 was included due to it being a dependency for the xfig which the 
transfig utility is part of.

If I were return to working on a bundled-app, I’d *might* still favor macports. 
But I’d make some important changes to reduce the size.
(1) With Yosemite most of the toolchain is Xcode. For fortran gcc is still 
needed. However, if the version of Xcode and gcc used are documented, it would 
not be necessary to include them.
(2) Include texinfo by constructing a trivial port/package for texinfo.
(3) Include transfig by constructing a trival port/package for transfig 
(without the rest of xfig and its dependencies).
(4) Exclude gnuplot since Octave now has native graphics.

I think a gnuplot app-bundle would also be a good idea.

My regular job is now keeping me very busy and I’ve added three kids at home 
since I worked on an app-bundle. Returning to this project is a significant way 
won’t be happening for me anytime soon. However, if there is some way I can be 
of help I’m up for assisting.

In any event, I also experienced an unexpected lack of “enthusiasm”. Mostly 
because the Mac OS X users in Octave’s community are happy with homebrew, fink, 
or macpots.. However, I’ve come to expect there are a large number of potential 
user for an app-bundle who are students with short term needs and are not privy 
the the octave community. I expect a reliable app-bundle would get a lot of use 
and would bring a lot of value, and would like to offer encouragement for your 
continued effort.

Ben