FS#45956 - [octave] optdepends description for qscintilla outdated?
Attached to Project:
Arch Linux
Opened by Lex Black (TrialnError) - Tuesday, 11 August 2015, 15:35 GMT
Last edited by Ronald van Haren (pressh) - Tuesday, 08 September 2015, 09:12 GMT
Opened by Lex Black (TrialnError) - Tuesday, 11 August 2015, 15:35 GMT
Last edited by Ronald van Haren (pressh) - Tuesday, 08 September 2015, 09:12 GMT
|
Details
Description:
Shouldn't the description for qscintilla be changed? Since 4.0 the GUI isn't experimental anymore. In fact it's the default now if octave get's called. If one want to use the cli versions he needs to use octave-cli or octave with the start-up options --no-gui or --no-gui-libs |
This task depends upon
Closed by Ronald van Haren (pressh)
Tuesday, 08 September 2015, 09:12 GMT
Reason for closing: Implemented
Additional comments about closing: 4.0.0-2
Tuesday, 08 September 2015, 09:12 GMT
Reason for closing: Implemented
Additional comments about closing: 4.0.0-2
Quote from the changelog:
"Octave now uses OpenGL graphics with Qt widgets by default. If OpenGL
libraries are not available when Octave is built, gnuplot is used.
You may choose to use the fltk or gnuplot toolkit for graphics by
executing the command
graphics_toolkit ("fltk")
OR
graphics_toolkit ("gnuplot")
Adding such a command to your ~/.octaverc file will set the default
for each session."
Which leaves the impression, that fltk could be an optdepend now.
Didn't check on that yet, but will probably later
Personally I wouldn't like such a move.
And changing the PKGBUILD and install files would be one-timer and could be done with a script (sed, add+commit, push). If the packages will work with no problems even if qscintilla is used. Or is there something else problematic?
As for fltk... octave seems to work without fltk installed and uses gnuplot just fine, but it throws an error in the main screen. Although this seems harmless, I'm not sure we would want an error to appear just after the application is started.
And regarding fltk. No, such a startup error-message isn't really encouraging, even it is working fine. Kinda reminds of the matplotlib dilemma (choose your backend freely.. well, ok not so free, as my default I set while building is needed)