From: raingloom <raingloom@riseup.net>
To: Katherine Cox-Buday <cox.katherine.e@gmail.com>
Cc: guix-devel@gnu.org, Sarah Morgensen <iskarian@mgsn.dev>
Subject: Re: Could the Go importer use the Go toolchain? (was Re: Go importer and packages with version flags)
Date: Sat, 2 Oct 2021 22:09:17 +0200 [thread overview]
Message-ID: <20211002220917.496806f1@riseup.net> (raw)
In-Reply-To: <87fstmcc77.fsf_-_@gmail.com>
On Thu, 30 Sep 2021 10:31:08 -0500
Katherine Cox-Buday <cox.katherine.e@gmail.com> wrote:
> Sarah Morgensen <iskarian@mgsn.dev> writes:
> > Did you have something particular in mind as far as leveraging the
> > Go tooling?
>
> I haven't though too much about it, but ~GOPROXY=direct~ was my guess
> too. Thinking about this, would a shallow fetch into a bare
> repository be so bad?
>
> It made me start wondering why our ~git-download~ type /doesn't/ have
> this behavior. Are we unnecessarily pulling down the entire commit
> history with all tags and branches of a large repository?
>
> I don't even know what the philosophy is being doing this or not.
> Isn't the only commitment a Guix package makes for software at a
> particular version/commit that the store contains that immutable
> version of the source, not the complete repository?
AFAIK there is a long standing libgit2 bug for adding support for
shallow fetches. Or rather operations on shallow repositories.
https://github.com/libgit2/libgit2/issues/3058
So guile-git can't have shallow fetches until libgit2 gets its act
together. Or Guix could use a patched libgit2 I guess.
next prev parent reply other threads:[~2021-10-02 20:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-27 21:51 Go importer and packages with version flags Jack Hill
2021-09-28 2:53 ` Katherine Cox-Buday
2021-09-28 5:47 ` Sarah Morgensen
2021-09-28 17:08 ` Katherine Cox-Buday
2021-09-30 3:17 ` Sarah Morgensen
2021-09-30 15:31 ` Could the Go importer use the Go toolchain? (was Re: Go importer and packages with version flags) Katherine Cox-Buday
2021-10-02 20:09 ` raingloom [this message]
2022-10-06 15:01 ` François
2022-10-22 13:23 ` Maxim Cournoyer
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=20211002220917.496806f1@riseup.net \
--to=raingloom@riseup.net \
--cc=cox.katherine.e@gmail.com \
--cc=guix-devel@gnu.org \
--cc=iskarian@mgsn.dev \
/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).