Re: Octave & QtOctave

[ng0]

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 <address@hidden> 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