On Sat, 30 Dec 2017, Dirk Eddelbuettel wrote:

On 29 December 2017 at 09:58, Riccardo (Jack) Lucchetti wrote:
|
| Using gtksourceview3 is already possible; actually, the default for the
| configure script is to prefer gtk3 over gtk2. Maybe it's just a matter of
| adjusting the debian-specific scripts?

Yes. It's all programmatic. A long time (5 years? 8 years?) ago I had issues
with gtk3 and just froze gretl it at gtk2.  Time to change.

Maybe, though in my opinion gretl is still better served by gtk2 than gtk3. It's true that gtksourceview2 has not been updated in a long time now (though gtk2 itself continues to be updated), but it works OK and I'm not aware of any substantial enhancements in gtksourceview3 that are relevant for gretl.

 Installation path:                      /usr
 Use readline library:                   yes
 Use gnuplot for graphs:                 yes
 Use pdflatex for typesetting:           yes
 Use libgsf for zip/unzip:               no
 sse2 support for RNG:                   no
 OpenMP support:                         yes
 MPI support:                            yes
 AVX support for arithmetic:             no
 Build with GTK version:                 3.0
 Build gretl documentation:              no
 Use Lucida fonts:                       no
 Build message catalogs:                 yes
 Build gretl addons:                     no
 X-12-ARIMA support:                     yes
 TRAMO/SEATS support:                    yes
 libR support:                           yes
 libsvm support:                         no
 ODBC support:                           yes
 JSON parsing support:                   yes
 Experimental audio support:             no
 Use xdg-utils in installation:          no

 LAPACK libraries:
   -llapack -lblas -lgfortran

Now type 'make' to build gretl. xdg-utils seems like a low-hanging fruit...

If you mean that enabling xdg-utils for installation might be good, I'd be careful with that: please check the manual for (e.g.) xdg-desktop-menu with its "install" option and ensure that it's compatible with your packaging practice. My understanding (which may be wrong) is that it will install things under (e.g.) /usr/share (which may not be what you want).

Allin Cottrell

Reply via email to