From: Leo Famulari <leo@famulari.name>
To: Csepp <raingloom@riseup.net>
Cc: phodina via <help-guix@gnu.org>
Subject: Re: Packaging Grafana
Date: Sun, 15 Jan 2023 12:47:37 -0500 [thread overview]
Message-ID: <Y8Q8OScBH26ygoni@jasmine.lan> (raw)
In-Reply-To: <86v8l8yrqp.fsf@riseup.net>
On Sun, Jan 15, 2023 at 12:12:40PM +0100, Csepp wrote:
> Honestly, I think our Go importer needs to be rewritten to just use Go's
> libraries instead of trying to replicate all functionality in Guile. It
> does a lot of... let's say sub-optimal things currently, like cloning
> full git repos, when Go is smart enough to only clone what it needs for
> dependency resolution.
If that would work, then sure. Whoever is motivated to do the work will
be the person (people?) who decides what happens.
next prev parent reply other threads:[~2023-01-15 17:48 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 [this message]
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
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=Y8Q8OScBH26ygoni@jasmine.lan \
--to=leo@famulari.name \
--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).