Karl Hallsby 31c13c07d2 octave.pkgs.level-set: init at 2019-04-13 ... 1) Version 0.3.0 has numerous bugs due to not being updated for nearly 5 years. So, I had to use fetchgit instead, grabbing HEAD of master. 2) level-set uses a non-standard layout for its files (no MAKEFILE in the root of the package for octave to use), but instead has a build.sh script to run. This script *JUST* generates a tarball that can THEN be used for `pkg build`. `patchPhase` performs some substitutions on this to make it generate the tarball in a way we expect it to. This tarball ends up in the /build directory we have available to us. 2.5) This script NEEDS automake, autoconf, and autoconf-archive to be available. This is unnecessary for other packages because Octave has a well-defined Makefile scheme that developers are supposed to follow that allows Octave to handle the building of packages. But this package breaks the mold. 3) With the tarball we use to build being available, we need to then `cd` back to the previous location (as the script takes us from `/build` to `/tmp`. So we go back using `cd -`. 4) Lastly, we can now use the standard `buildPhase` defined for `buildOctavePackage` and complete the building of level-set. Hopefully, this will be fixed in a later release, so it is easier to maintain. 10/260 tests FAIL, where most of those 10 are due to improper usage of the parallel package. Overall, I believe this is a reasonable amount of passing tests to allow this to be marked as working.		2021-02-24 21:00:50 +02:00
..
default.nix