From: Saku Laesvuori <saku@laesvuori.fi>
To: Distopico <distopico@riseup.net>
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>, guix-devel@gnu.org
Subject: Re: Guix and the developer ecosystem
Date: Tue, 8 Aug 2023 19:59:29 +0300 [thread overview]
Message-ID: <20230808165929.5vyih2ry3ezleayf@X-kone> (raw)
In-Reply-To: <87pm42mfp8.fsf@riseup.net>
[-- Attachment #1: Type: text/plain, Size: 799 bytes --]
>> Certainly, Nix enjoys clout, but there's nothing to stop you from
>> committing a guix.scm to your favourite project. Case in point, I
>> recently contributed to one such project on Github (via mail to the
>> devs, of course).
>
>Well, what holds me back is that many dependencies are missing, such as
>the basic ones I mentioned, making it impossible to use Guix in many
>cases. [...] So, it's not
>feasible to include that in the project due to current limitations.
You could add the missing dependencies to the guix.scm. I often have ten
or so dependencies in my haskell projects' guix.scm files. It takes a
bit of time because the recursive hackage importer is currently broken
(https://issues.guix.gnu.org/64734), but it's not too bad because guix
already has most of the common packages.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-08-08 17:00 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 [this message]
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
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=20230808165929.5vyih2ry3ezleayf@X-kone \
--to=saku@laesvuori.fi \
--cc=distopico@riseup.net \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@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).