From: zimoun <zimon.toutoune@gmail.com>
To: Phil <phil@beadling.co.uk>,
Liliana Marie Prikler <liliana.prikler@gmail.com>
Cc: Guix Devel <guix-devel@gnu.org>
Subject: Re: Help to workaround libgit2 fetch refs issue
Date: Sat, 30 Apr 2022 11:28:57 +0200 [thread overview]
Message-ID: <865ymqq5ra.fsf@gmail.com> (raw)
In-Reply-To: <8735jwharw.fsf@beadling.co.uk>
Hi Phil,
On Sat, 05 Mar 2022 at 11:57, Phil <phil@beadling.co.uk> wrote:
> (git-checkout
> (url "ssh://git@bitbucket:7999/foo/bar.git")
> (commit commit-production)))
Why this is not enough for your use case? As mentioned in [1].
1: <https://issues.guix.gnu.org/issue/31285#4>
> This is covered here I think, and a patch was proposed, but it was
> dropped in favour for the original solution above in the original thread:
> http://issues.guix.gnu.org/issue/31285
The closing message says:
Yes, this does work. Combined with the fact that it is now
possible to "guix pull" channels over SSH, there is no need for
this patch any more. The "git-checkout" gexp-compiler basically
does the same thing that I was trying to do (it is still
"impure" in that the fetching happens outside the store), but it
does it more elegantly.
<https://issues.guix.gnu.org/issue/31285#6>
so instead of…
> I did think about perhaps resurrecting the proposed "git-fetch/impure"
> as shown in the patch of guix-download.scm in the link immediately
> above, but I was hoping for a quicker win with duplicating the record -
> alas that has it's own significant limitations tho.
…maybe the location is “git-checkout” gexp-compiler and see what is
missing for covering your use-case.
Cheers,
simon
prev parent reply other threads:[~2022-04-30 9:34 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-02 18:31 Help to workaround libgit2 fetch refs issue Phil
2022-03-02 21:06 ` Liliana Marie Prikler
2022-03-03 18:20 ` Phil
2022-03-04 9:34 ` Phil
2022-03-04 17:43 ` Liliana Marie Prikler
2022-03-05 11:57 ` Phil
2022-04-30 9:28 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=865ymqq5ra.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=guix-devel@gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=phil@beadling.co.uk \
/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 external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.