From: zimoun <zimon.toutoune@gmail.com>
To: mail@brendan.scot, guix-devel@gnu.org,
Maxime Devos <maximedevos@telenet.be>, John Soo <jsoo1@asu.edu>
Subject: Re: Improving importers best investment for growing gnu/packages/
Date: Mon, 02 May 2022 11:19:15 +0200 [thread overview]
Message-ID: <87levk9trg.fsf@gmail.com> (raw)
In-Reply-To: <e9c52497-3fae-5e22-928b-0ecc6018fbee@brendan.scot>
Hi,
On Tue, 29 Mar 2022 at 10:50, Brendan Tildesley <mail@brendan.scot> wrote:
> Therefore I'm working on making use of
> https://github.com/rust-lang/crates.io-index to fully import base definitions
> all required crates rather than pulling metadata from the internet with each refresh.
From my point of view, the issue is that it requires external Rust tools
and I think such tool will never be part of the Guix dependencies. Guix
itself cannot depends on Rust-thing, GHC-thing, OCaml-thing,
Julia-thing, etc. because they ease the importers.
And that’s why the current importers parse metadata and somehow
“reimplement” the logic behind the package manager of each language. I
agree that it is a lot of work and hard to maintain but doing so allow
Guix to have a small footprint (dependency, speaking).
That’s said, how to improve the importers?
Well, Guix provides now GUIX_EXTENSIONS_PATH which allows to extend by
other subcommands. “guix workflow” is an example, I do not remember how
“guix home” did initially, anyway!
My point is: this mechanism allows to have a package (with many
dependencies) extending Guix itself. Somehow, it reads
guix install guix-rusty
guix rusty <stuff>
where ’guix-rusty’ would be a Guile package (program) using whatever it
needs from the Rust ecosystem (say parse system calls of cargo or
whatever).
Guix is Scheme library after all, let use it! :-)
Cheers,
simon
prev parent reply other threads:[~2022-05-02 9:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-25 8:05 Packaging rust-analyzer is not necessary Paul Alesius
2022-03-26 15:30 ` Maxime Devos
2022-03-26 16:33 ` John Soo
2022-05-09 19:06 ` Maxime Devos
2022-03-28 23:50 ` Improving importers best investment for growing gnu/packages/ Brendan Tildesley
2022-03-29 9:01 ` Maxime Devos
2022-03-29 10:30 ` Brendan Tildesley
2022-03-29 19:03 ` Liliana Marie Prikler
2022-05-02 9:19 ` zimoun [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=87levk9trg.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=jsoo1@asu.edu \
--cc=mail@brendan.scot \
--cc=maximedevos@telenet.be \
/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).