From: ng0@n0.is
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Octave & QtOctave
Date: Sat, 24 Nov 2018 22:10:22 +0000 [thread overview]
Message-ID: <20181124221022.ankjuz4mdpkoohkn@abyayala> (raw)
In-Reply-To: <87a7lyzkk2.fsf@gmail.com>
names for packages are (mostly) random, although in some
cases following classiifcations (see python-*, r-*, ...).
The Qt part of Octave is a separate package because making
it just an output would still pull in Qt and the size difference
is huge.
Alex Vong transcribed 856 bytes:
> Hello,
>
> Brett Gilio <brettg@posteo.net> writes:
>
> > Hey all,
> >
> > Happy guix birthday!
> >
> > Quick question, why is the octave package split up into two different
> > public definitions, rather than just having the QtOctave-GUI being a
> > "gui" output, like it is for transmissionBT and some others?
> >
> I would also want to know why it is called qtoctave. My understanding is
> that qtoctave was a GUI frontend to the official octave which is now
> replaced by the official octave GUI.
>
> > Best,
> > Brett Gilio
>
> Cheers,
> Alex
next prev parent reply other threads:[~2018-11-24 22:10 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-24 0:56 Octave & QtOctave Brett Gilio
2018-11-24 13:12 ` Alex Vong
2018-11-24 22:10 ` ng0 [this message]
2018-11-25 14:12 ` Should we rename qtoctave to octave and octave to octave-cli? (was Re: Octave & QtOctave) Alex Vong
2018-11-25 15:49 ` Brett Gilio
2018-11-25 15:58 ` Octave & QtOctave Ludovic Courtès
2018-11-27 17:53 ` Kei Kebreau
2018-11-28 10:47 ` Ludovic Courtès
2018-11-29 16:21 ` swedebugia
2018-12-02 19:25 ` Kei Kebreau
2018-12-02 19:28 ` Kei Kebreau
2018-12-02 21:18 ` swedebugia
2018-12-03 1:07 ` Kei Kebreau
2018-12-04 14:17 ` Alex Vong
2018-12-04 20:53 ` Kei Kebreau
2018-12-06 5:30 ` Alex Vong
2018-12-06 15:42 ` Kei Kebreau
2018-12-06 17:50 ` Alex Vong
2018-12-07 15:52 ` Kei Kebreau
2018-12-08 18:23 ` Kei Kebreau
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181124221022.ankjuz4mdpkoohkn@abyayala \
--to=ng0@n0.is \
--cc=alexvong1995@gmail.com \
--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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.