unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Efraim Flashner <efraim@flashner.co.il>
To: David Pirotte <david@altosw.be>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: octave: Update to 4.0.2.
Date: Wed, 18 May 2016 20:23:03 +0300	[thread overview]
Message-ID: <20160518172303.GA14019@debian-netbook> (raw)
In-Reply-To: <20160517234301.51e8b063@capac>

[-- Attachment #1: Type: text/plain, Size: 1143 bytes --]

On Tue, May 17, 2016 at 11:43:01PM -0300, David Pirotte wrote:
> Hello,
> 
> > Small update for GNU Octave. Hopefully in the future we can include the
> > GUI.
> 
> 	I'm not a guix developer, neither a guix user yet, but I follow #guix and
> 	this list, to get prepared :) and read good advice and good guile
> 	scheme techniques...
> 
> So, starting with version 4.0.x, octave _does_ include a GUI by default, and it
> launches itself using this GUI by default [which is a terrible shame afaic, but
> that's not the opinion of the octave developers].
> 
> So the GUI is in your package, and people who would want to use octave the good old
> way, in a terminal or in emacs inferior mode much launch it with the --no-gui option.
> 
> Hope this info is useful,
> David

What toolchain do they use to build the GUI? There isn't anything listed
in the inputs like gtk+-2 (as seems standard for GNU projects).


-- 
Efraim Flashner   <efraim@flashner.co.il>   אפרים פלשנר
GPG key = A28B F40C 3E55 1372 662D  14F7 41AA E7DC CA3D 8351
Confidentiality cannot be guaranteed on emails sent or received unencrypted

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

  reply	other threads:[~2016-05-18 17:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-05-18  0:41 [PATCH] gnu: octave: Update to 4.0.2 Kei Kebreau
2016-05-18  2:43 ` David Pirotte
2016-05-18 17:23   ` Efraim Flashner [this message]
2016-05-18 19:31     ` David Pirotte
2016-05-19  1:35 ` Efraim Flashner

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20160518172303.GA14019@debian-netbook \
    --to=efraim@flashner.co.il \
    --cc=david@altosw.be \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).