unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
To: zimoun <zimon.toutoune@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: naming scheme for "compilers" toolsuite?
Date: Fri, 15 May 2020 12:46:26 -0400	[thread overview]
Message-ID: <CAFkJGRf6JtdLV4beKr=WTpMWBfmJ_AVTGThmSK-_k2d_MG5O2Q@mail.gmail.com> (raw)
In-Reply-To: <CAJ3okZ0i0DjQMzgJ9WwzDC2tKc8WeTZxqW46KH+vq9zKbgBzhQ@mail.gmail.com>

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

Bringing back this necrothread, what you are suggesting is something I
would find intuitive.  Sounds like a good idea to me.

On Thu, Apr 16, 2020, 22:12 zimoun <zimon.toutoune@gmail.com> wrote:

> Dear,
>
> Giving a look to the Arun's patches [1] about improving "guix search",
> I am testing some queries. Well, I am not able to find what I want in
> the jungle of all the packages, independently of the implementation of
> "guix search".
>
>
> For example, what is the package which provides standard libraries and
> tools for Haskell? for OCaml?
>
>
> Does the package named "ghc-toolchain" or "haskell-toolchain" seem a good
> idea?
> Debian provides the package named "haskell-platform" which gives a
> nice batteries included Haskell experience.
>
> Note that Guix already provides "gcc-toolchain" or "clang-toolchain"
> or "gfortran-toolchain". Therefore, it seems consistent to provide
> something similar for Haskell and OCaml, say. Maybe more.
>
> Last, from the "guix search haskell" it is hard to know which packages
> to install and then to have an easy Haskell experience. The package
> "ghc" is the sixth on the list.
>
>
> What do you think?
>
> All the best,
> simon
>
> [1] https://issues.guix.gnu.org/issue/39258#68
>
>

[-- Attachment #2: Type: text/html, Size: 1816 bytes --]

      reply	other threads:[~2020-05-15 16:46 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-17  2:12 naming scheme for "compilers" toolsuite? zimoun
2020-05-15 16:46 ` Josh Marshall [this message]

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='CAFkJGRf6JtdLV4beKr=WTpMWBfmJ_AVTGThmSK-_k2d_MG5O2Q@mail.gmail.com' \
    --to=joshua.r.marshall.1991@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=zimon.toutoune@gmail.com \
    /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).