Package Details: matlab 9.9.0.1467703-1

Git Clone URL: https://aur.archlinux.org/matlab.git (read-only, click to copy)
Package Base: matlab
Description: A high-level language for numerical computation and visualization
Upstream URL: http://www.mathworks.com
Keywords: matlab
Licenses: custom
Provides: matlab-bin, matlab-engine-for-python, matlab-licenses
Submitter: ido
Maintainer: bbaserdem
Last Packager: bbaserdem
Votes: 26
Popularity: 0.22
First Submitted: 2015-08-15 09:33
Last Updated: 2020-09-29 21:42

Dependencies (63)

Required by (4)

Sources (1)

Pinned Comments

bbaserdem commented on 2020-09-21 16:39

New users: PLEASE read the README.md file contained in the PKGBUILD repo, as the packaging details are changed and you will find instructions.

Existing users: Please help me test and trim the dependencies list, and submit your personal fixes for issues if you have them so they can be added to the PKGBUILD.

New users would be pre-r2020a users of this pkgbuild.

Latest Comments

1 2 3 4 5 6 ... Next › Last »

kyak commented on 2020-10-02 08:56

@daniel_shub you can request a trial version of MATLAB here: https://www.mathworks.com/campaigns/products/trials.html

daniel_shub commented on 2020-09-30 16:32

@bbaserdem as you say, running my example check function from within the PKGBUILD is difficult because of potential differences in the hardware on the build machine and the target machine and it probably would not tell you much about how MATLAB will behave on the target machine. Running the check on the build machine also would require activating MATLAB on the build machine which introduces other problems. That is why I did not include the check function originally when I created the package.

I think having an additional script that tests the MATLAB installation on the target machine is probably the way to go. This way a system administrator who is asked to install MATLAB on the target machine can be reasonably confident that the software works on the target hardware even if they do not understand MATLAB. Of course this is extra work but it would resolve questions like the one by @rellieberman. I wish I had a newer version of MATLAB so that I would not have been forced to neglect the package for all those years and could help out with writing a test function, because as I think everybody realizes, getting MATLAB to work in Arch is tricky.

bbaserdem commented on 2020-09-30 15:58

The activation and licensing completely is disengaged from the PKGBUILD. You have to do that manually yourself; which I documented in the README.md. If you install the created package on a machine that is different than the licensed one, you won't be able to run the package. And as long as you don't redistribute (and that is fully on you; not the AUR) the built package; you are compliant with the EULA. Just to be 100% sure; you need to remove the matlab tar.zst from the pacman cache; but you won't go to jail if you don't do that.

There are absolutely no files distributed through the AUR; this is just an installation script. This PKGBUILD is not a matlab installation hack; it's a matlab-pacman integration at best; and fixes some behavioral issues for you. This is not meant to be portable due to how the EULA works; you are not supposed to port it anywhere. However; what you can do is you can run this package on some computer B; but prepare the outlying package to be installed on computer A. As long as you keep your copies to yourself; you are fully within the EULA. Robustness wise; this is the recommended installation procedure from the MATLAB website regarding installing without an active internet connection so that I don't agree with; it's the proper way to do so.

The check function is a good suggestion for things like compatible python version and whatnot, I'll see what I can come up with based on your suggestion. Hardware tests would not be good practice; as there is no guarantee that the computer that will run the built package is the same as the one doing the packaging; not to mention the makepkg user usually does not have access to hardware interfaces. Not to mention not all hardware will support every feature (can't run gpu array on one of my PC's, hardware acceleration and audio is disabled on my server, not everyone wants all the features, etc.

Maintenance wise; I have seen this package neglected over the past few years. While i'm working at the lab I'm in (for another year) and while I actively use Arch as my desktop distribution; I am planning on maintaining this package and won't share maintenance with someone else unless I can trust them. But I will most likely maintain it for another year, a year and a half at most, and then pass it on to someone with motivation to provide.

daniel_shub commented on 2020-09-30 15:11

I think the package would benefit from a check function or an extra script that checks the installation. When I originally created the PKGBUILD, I toyed with including the following

checkdepends=(xorg-fonts-100dpi cuda)
check () {
  _matlab_cmd="/bin/matlab -nodesktop -nosplash -r"
  LC_ALL=C $matlab_cmd "version -java, exit" | grep Java
  LC_ALL=C $matlab_cmd "opengl info; exit" | grep Software
  LC_ALL=C $matlab_cmd "x=rand(10, 'single'); g=gpuArray(x); Success=isequal(gather(g), x), exit"  | sed -ne '/Success =/,$p'
  LC_ALL=C $matlab_cmd "doc doc; pause; exit"
  LC_ALL=C $matlab_cmd "xlabel('BIG FONT', 'FontSize', 42); ylabel('small font', 'FontSize', 12); pause; exit" > /dev/null
  LC_ALL=C $matlab_cmd "bench, pause; exit" > /dev/null
  LC_ALL=C $matlab_cmd "load handel; sound(y, Fs); pause(length(y)/Fs); exit" > /dev/null
}

but dealing with the licensing and activation in makepkg did not seem robust or portable, and probably violates the MATLAB ELUA. That said, I did manually run those tests (along with namcap) on my machine before updating the PKGBUILD to make sure it worked. I would incrementally add dependencies until the package would pass those tests.

Most of the above script is documented in the MATLAB Arch wiki and covers most of my MATLAB use cases. I just looked at the wiki now and it seems like a more complete check/test function would include tests for the compiler(s), serial port, static TLS issues, addon manager (this is apparently where the libselinux package is needed), live script, and webcam support. I do not have a license for newer versions of MATLAB, so can no longer maintain the package or really help with the tests.

bbaserdem commented on 2020-09-30 14:52

I'll run it myself once it's OK for me to do so (when i'm not actively using matlab and free time) In the meantime; anyone wishing to skip libselinux installation can try removing from the dependency array for now.

rellieberman commented on 2020-09-30 14:17

Thanks for the quick response. I would just point out that the installer ran fine on my system without libselinux. Is there anything I could test to help make sure it works?

(I installed very few of matlabs components so maybe it's needed for some other component. but again installer worked fine)

bbaserdem commented on 2020-09-30 14:04

libselinux is needed to run the installer; it's just the library component and is NOT selinux. You don't need to set it up. It is also listed as a dependency in the docker build images. I can double check if everything works fine without libselinux for 2020b and remove it if it doesnt break (less aur dependencies, the better); but previously with 2020a on arch; the installer would not run without libselinux which was confounding as there was no documentation on that dependence and installer. (Their official supported distro is Ubuntu; and I assume Ubuntu has libselinux by default)

Even if the main binary does not need it; you need to run the installer yourself at least once; so i consider that as a dependency.

rellieberman commented on 2020-09-30 13:57

Hi, thanks for this package :)

Does anyone know why libselinux is a dependency? I have just installed this package without the selinux dependency and all seems to be working fine. Seem like quite an overhead to have to install selinux just to run matlab.

bbaserdem commented on 2020-09-29 21:43

@ruy16109 thanks for bringing attention. I replaced the name with mcc-matlab so it should not happen. If you can confirm it works fine that would be great.

ruy16109 commented on 2020-09-28 14:59

The new matlab PKGBUILD conflicts with mathematica because both try to own /usr/bin/mcc.

Matlab version: 9.9.0.1467703-1 Mathematica version: 12.1.0-1 (not yet updated because it takes ages, but I assume the same would happen)