unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: swedebugia <swedebugia@riseup.net>
To: guix-devel@gnu.org
Subject: Re: Octave & QtOctave
Date: Thu, 29 Nov 2018 17:21:31 +0100	[thread overview]
Message-ID: <e998963b-3763-c7ea-d3d9-c3b574a40109@riseup.net> (raw)
In-Reply-To: <87va4h5vhr.fsf@gnu.org>

On 2018-11-28 11:47, Ludovic Courtès wrote:
> Kei Kebreau <kkebreau@posteo.net> skribis:
snip

>>
>> I agree with ng0 that Octave and its GUI interface should be kept in
>> separate packages, as the difference in size is more than 5000 MiB.
>> I also agree that the GUI package should be named "octave", but I don't
>> know whether the CLI package should be named "octave-minimal" or
>> "octave-cli".  I find myself leaning toward "octave-cli" because the CLI
>> package does include some non-essential dependencies.
> 
> Makes sense to me.  If others agree with this (“octave-cli” rather than
> “octave-minimal”), go ahead!

I agree.

-- 
Cheers
Swedebugia

  reply	other threads:[~2018-11-29 16:15 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
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 [this message]
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

  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=e998963b-3763-c7ea-d3d9-c3b574a40109@riseup.net \
    --to=swedebugia@riseup.net \
    --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).