Package Managers

• APT Package Manager - For Debian, Mint, Ubuntu, Xubuntu, there is a *.deb package.

• Slackpkg Package Manager - For Slackware, the best approach is to build from the source (see next section).

• Pacman Package Manager - For Arch the best approach is to build from the source (see next section).

• RPM, Yast2, Zypper Package Manager - For CentOs, Redhat Enterprise, OpenSuse there is an *.rpm package.
• Apple Package Management - For users with Apple products like the MacBook Pro, the best approach is to build from the source. The Apple environment has a number of package managers (Fink, Brew, MacPorts), and detection of the Darwin system is included in the configuration script. Because there are multiple possible package management instances in a single system, the user is cautioned to avoid crashing installed directories. The next section gives an example of how installation on a MacBook Pro can be done.

• Microsoft Package Manager - There is no install wizard. For Windows XP or Windows 8.1, the user may download a ZIP archive of static compiled *.exe files. These have been cross-compiled on a Linux host using the MingW32 tool chain. Simply download BSU_EXEC.zip and unzip the archive in an executable directory which is in your execution path. The man pages are available for download in man-bsu3-html.zip and can be viewd using a web browser. The Octave scripts are available in Octave.zip, but some codes will not work if they require disper.oct. To build that, you will need a windows equivalent of mkoctfile on your system, in addition to a windows version of Octave. I recommend that the windows user run the codes in a PowerShell environment. Further, to increase the utility of the codes, I recommend that the user install a windows MingW32 package. CAUTION: Windows is not a true case sensitive system, and both upper and lower case names will be viewed as being the same.

• Chrome Books and APT Package Management - For Chrome book users, the source can be compiled if developer mode is installed. Be aware of your CPU (Intel or Arm), since you will want to make sure any dependencies are met with the same CPU. I was able to compile on a Samsung Chrome Book set to developer mode with Crouton and XFC4 window manager, and an armv7l CPU. See the next section for more details.