unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Alex Vong <alexvong1995@gmail.com>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: Octave & QtOctave
Date: Sun, 25 Nov 2018 16:58:11 +0100	[thread overview]
Message-ID: <87k1l1w3n0.fsf@gnu.org> (raw)
In-Reply-To: <20181124221022.ankjuz4mdpkoohkn@abyayala> (ng0's message of "Sat, 24 Nov 2018 22:10:22 +0000")

Hello,

ng0@n0.is skribis:

> names for packages are (mostly) random, although in some
> cases following classiifcations (see python-*, r-*, ...).

That randomness is very limited in practice, if I may.  :-)

  https://gnu.org/software/guix/manual/en/html_node/Package-Naming.html

“qtoctave” was added by Kei.  WDYT about the naming issue, Kei?

Ludo’.

  parent reply	other threads:[~2018-11-25 15:58 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     ` Ludovic Courtès [this message]
2018-11-27 17:53       ` Octave & QtOctave 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

  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=87k1l1w3n0.fsf@gnu.org \
    --to=ludo@gnu.org \
    --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 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).