forge tester: Flatpak sandboxing hides results files

[apjanke]

The results files for this go into /tmp/<whatever>. But in a Flatpak-installed Octave, it seems like the filesystem is sandboxed/virtualized and that /tmp is redirected.

octave:5> testify.install_and_test_forge_pkgs
Log file: /tmp/octave-testify-ForgePkgTester/octave-testify-ForgePkgTester-2019-03-16_18-34-40/test_all_forge_pkgs.log

But:

janke@ubix:~ $ ls /tmp/octave*
zsh: no matches found: /tmp/octave*

Figure out a good way to expose these result files under Flatpak on Linux. We need Flatpak support because that seems to be the only good way to install a recent Octave on Linux.

References:

• Flatpak Sandbox Permissions

[apjanke]

I suppose I could just stick the results in ~/octave/testify/forge-tester/results. Writes to ~ work under Flatpak Octave.

[apjanke]

Well, now that I upgraded my Flatpak Octave to 5.1.0, it won’t install .zip file packages any more.

janke@ubix:~ $ flatpak run org.octave.Octave
[...snip...]
GNU Octave, version 5.1.0
[...snip...]

octave:1> pkg install https://github.com/apjanke/octave-testify/archive/master.zip
unpack: unarchiving program exited with status: 2
tar: This does not look like a tar archive
tar: Skipping to next header
tar: Exiting with failure status due to previous errors
error: called from
    unpack at line 274 column 5
    untar at line 48 column 5
    install at line 81 column 9
    pkg at line 441 column 9
octave:1> 

Luckily, this seems to work:

octave:1> pkg install https://github.com/apjanke/octave-testify/archive/master.zip

[apjanke]

I stuck the output in ~/octave/testify: https://github.com/apjanke/octave-testify/commit/4aabc5d972792eba4fc4a253f95d399cac5a09a3.

Maybe I should do the same change on macOS for consistency.

[apjanke]

Gonna leave it as is on macOS for now. Calling this fixed.