Documentation missing

[kupiqu]

I get the following error:

The info file
/app/share/info/octave.info
or compressed versions do not exist

[kupiqu]

Thanks for the info. I hope this can be fixed somehow in the near future (hopefully by the time Octave 4.4 is released).

[mtmiller]

I believe the intent for 4.4 is to try to build a Qt help file format and use a Qt help browser widget for the GUI, leaving the GNU info format for command-line mode. That is a work in progress over the last week or so.

[kupiqu]

I see, that's interesting!

So Mike, do you think this issue is also upstream, then?

[mtmiller]

It's upstream as long as we get that resolved!

It's a flatpak issue in that the plaintext info browser does work for me as-is in a non-flatpak build of Octave. So let's leave this open in case we do need to address that. I'll be building this regularly over the coming days and trying to repro some of these issues, and keep an eye on the upstream GUI development tasks.

[mtmiller]

Link to upstream issue working on help widget.

[mtmiller]

Link to upstream issue just filed on failure to install user manual in Info format.

[mtmiller]

I will try to look into adding an updated version of GNU Texinfo to the build as a workaround in case the GUI doc browser stays the way it is and needs the info files installed.

[kupiqu]

I see. I wonder, couldn't the flatpak package be linked to texinfo 6.1 instead?

EDIT: we crossed comments

[kupiqu]

I will try to look into adding an updated version of GNU Texinfo to the build as a workaround in case the GUI doc browser stays the way it is and needs the info files installed.

Great! if you do that, would it be very hard to update as well Octave version to current stable? It would allow me to further test issue #7

[mtmiller]

I only have enough bandwidth at the moment to test and rebuild with the rolling stable release myself. @Alexander-Wilms is taking care of the builds, and I have no idea how or when they are pushed to the flathub repo for public consumption.

[mtmiller]

I'm ok with whatever you think works best, I'm ignorant of the automation and how the branch name affects builds and the flathub repo.

Just let me know where to push or whether I should start using feature branches and PRs, whatever workflow you want to use.

[kupiqu]

Nice!