From: Distopico <distopico@riseup.net>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Guix and the developer ecosystem
Date: Fri, 18 Aug 2023 12:16:27 -0500 [thread overview]
Message-ID: <87h6ow9s5e.fsf@riseup.net> (raw)
In-Reply-To: <87o7j75apf.fsf@gnu.org>
On 2023-08-16, Ludovic Courtès <ludo@gnu.org> wrote:
> Hi,
>
> A late reply…
>
> Distopico <distopico@riseup.net> skribis:
>
>> 1. Are there plans in the future to improve integration between
>> development tools? For example, having haskell-language-server for
>> ghc@9.x and another one for ghc@8.x, or something similar to the
>> overwrite feature in Nix flake?
>
> I don’t think the project makes “plans” for such things. To me, it
> looks like mostly a matter of packaging; if ‘haskell-language-server’ is
> missing, then some Haskeller may eventually feel the need to package it.
> You can hope it’ll be someone else, but perhaps you’ll find that doing
> it yourself is worth trying. :-)
>
> Regarding customization, ‘--with-input’ and perhaps other transformation
> options may correspond to your needs:
>
> https://guix.gnu.org/manual/devel/en/html_node/Package-Transformation-Options.html
>
According with the docs, it will make rebuilt the packages so with
Rust/haskell that could take time and cpu, and for sure is a good option
in many cases, and maybe with Parameterized Packages[1] would be another
option, but what about have let said two packages like
`haskell-language-server-8.x` and `haskell-language-server-9.x` wherein
each one utilizes a predefined GHC version and prebuilt derivations? Is
this approach valid?
>> 2. Do you see developers as a potential target audience for Guix, or is
>> it mainly focused on HPC (High-Performance Computing)?
>
> My dayjob has to do with HPC and I think Guix is a good fit for them.
>
> But developers, whether in HPC or not, are definitely a target audience
> IMO. I believe Guix has great tools for development; that’s the spirit
> of this blog post:
>
> https://guix.gnu.org/en/blog/2023/from-development-environments-to-continuous-integrationthe-ultimate-guide-to-software-development-with-guix/
>
> Thanks for your feedback!
>
> Ludo’.
thank you for your response.
[1]: https://blog.lispy.tech/parameterized-packages-the-second-update.html
next prev parent reply other threads:[~2023-08-18 17:29 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-27 0:29 Guix and the developer ecosystem Distopico
2023-07-29 19:48 ` Liliana Marie Prikler
2023-08-05 1:11 ` Distopico
2023-08-05 17:29 ` Liliana Marie Prikler
2023-08-05 19:48 ` (
2023-08-05 20:12 ` Liliana Marie Prikler
2023-08-08 16:59 ` Saku Laesvuori
2023-07-31 9:42 ` (
2023-08-05 1:49 ` Distopico
2023-08-05 6:10 ` Julien Lepiller
2023-07-31 18:55 ` Wilko Meyer
2023-08-05 1:40 ` Distopico
2023-08-16 14:22 ` Ludovic Courtès
2023-08-18 17:16 ` Distopico [this message]
2023-08-24 15:01 ` Ludovic Courtès
2023-08-29 18:42 ` Distopico
2023-08-19 8:29 ` Simon Tournier
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=87h6ow9s5e.fsf@riseup.net \
--to=distopico@riseup.net \
--cc=guix-devel@gnu.org \
--cc=ludo@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).