From: Simon Tournier <zimon.toutoune@gmail.com>
To: Csepp <raingloom@riseup.net>
Cc: Csepp <raingloom@riseup.net>, phodina via <help-guix@gnu.org>
Subject: Re: libgit2 shallow clone (was Re: Packaging Grafana)
Date: Mon, 16 Jan 2023 17:34:24 +0100 [thread overview]
Message-ID: <87k01mtp4f.fsf@gmail.com> (raw)
In-Reply-To: <87wn5mzcnu.fsf@riseup.net>
Hi,
On lun., 16 janv. 2023 at 17:02, Csepp <raingloom@riseup.net> wrote:
> It would be worth it for importers. If I remember correctly, the
> reasoning for writing importers as Guile modules is reducing Guix's
> closure size, but that's nonsense when it comes to importing packages,
> because 99.9999% of the time you are going to be using the language's
> tooling anyways, because you will want to actually compile those
> imported packages.
> The Rust importer already loads guile-json or whatever at runtime, there
> is nothing wrong with having a similar runtime-only dependency on the Go
> compiler.
To add on this point, please also note that Subversion is required for
“guix import tex” (and probably also for packages using ’svn-fetch’).
Well, I think that Guix should be more modular using more extensions.
It would allow both of the 2 constraints: for one a small closure for
Guix proper and for two many external tools often required by importer.
Cheers,
simon
next prev parent reply other threads:[~2023-01-16 18:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-15 9:18 Packaging Grafana phodina via
2023-01-15 11:12 ` Csepp
2023-01-15 17:47 ` Leo Famulari
2023-01-16 11:39 ` libgit2 shallow clone (was Re: Packaging Grafana) Simon Tournier
2023-01-16 16:02 ` Csepp
2023-01-16 16:34 ` Simon Tournier [this message]
2023-01-15 17:46 ` Packaging Grafana Leo Famulari
2023-01-21 16:37 ` Katherine Cox-Buday
2023-01-21 16:47 ` Katherine Cox-Buday
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=87k01mtp4f.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=help-guix@gnu.org \
--cc=raingloom@riseup.net \
/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.
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).