From: wolf <wolf@wolfsden.cz>
To: Simon Tournier <zimon.toutoune@gmail.com>
Cc: guix-devel@gnu.org, "Ludovic Courtès" <ludo@gnu.org>
Subject: Re: hard dependency on Git? (was bug#65866: [PATCH 0/8] Add built-in builder for Git checkouts)
Date: Mon, 11 Sep 2023 19:51:15 +0200 [thread overview]
Message-ID: <ZP9Tk1K37Rv8qqv2@ws> (raw)
In-Reply-To: <871qf4ivsr.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 3007 bytes --]
On 2023-09-11 17:17:24 +0200, Simon Tournier wrote:
> Hi,
>
> On Mon, 11 Sep 2023 at 16:23, Ludovic Courtès <ludo@gnu.org> wrote:
>
> > Note that the patch series adds a hard dependency on Git.
> > This is because the existing ‘git-fetch’ code depends on Git,
> > which is itself motivated by the fact that Git supports
> > shallow clones and libgit2/Guile-Git doesn’t.
>
> Going this path, I appears to me worth to revisit the proposal:
>
> RFC: libgit2 is slow/inefficient; switch to git command?
> Maxim Cournoyer <maxim.cournoyer@gmail.com>
> Mon, 21 Nov 2022 21:21:02 -0500
> id:87cz9fpw4x.fsf@gmail.com
> https://yhetil.org/guix/87cz9fpw4x.fsf@gmail.com
> https://lists.gnu.org/archive/html/guix-devel/2022-11
>
> I know it is not an option for now to parse the output of ’git’ commands
> in order to keep the features of (guix git), (guix channels), etc.
>
> However, this discussion was mentioning an implementation of
> clone/checkout in pure Racket supporting shallow checkout. Considering
> the current level of integration, I thought the next Big Plan™ was to
> gradually move bits of Guile-Git to being pure Scheme, maybe based on
> the Racket implementation of ’clone’ as a starting point.
>
> Personally, I do not have a strong opinion about the Big Plan™. I note
> that the introduction of Git as a hard dependency is a slippery slope
> considering the current state of libgit2. Here, it starts with “git
> clone”, then “git gc” (unsupported by libgit2) is also in the pipes
> (#65720 [1]). And after timing, I am almost sure that many operations
> using Guile-Git will be slower than their plain Git counter-parts. And
> we will start to parse the output of ’git’ plumbing commands.
If you don't mind me asking, why is that so problematic approach? Git's
plumbing commands are intended to be used in scripts, so I am unsure what the
problem is.
I cannot recall a single instance when some tooling I have at home or wrote for
work stopped working due to git changing. I guess there likely are such
instances, but would be interested in examples if someone has a list.
> Slippery slope for pushing Guile-Git out, no?
Guile-git does not seem to be in the best place currently, when I was putting
together the script I sent to #65720, I tried to use the info manual, and the
best way to describe it is "incomplete". Some behaviors are... surprising.
Arguably that is the impression I got based on one morning of trying to use it,
so it is probably inaccurate description and lacks some details.
>
> And I do not speak about the closure. Is it possible to extract the
> command ’git-clone’ from git-minimal? It would reduce the size, no?
>
>
> Cheers,
> simon
>
> 1: https://issues.guix.gnu.org/65720
>
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-09-11 17:52 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-11 15:17 hard dependency on Git? (was bug#65866: [PATCH 0/8] Add built-in builder for Git checkouts) Simon Tournier
2023-09-11 17:51 ` wolf [this message]
2023-09-11 18:26 ` Maxim Cournoyer
2023-09-11 22:48 ` comparing commit-relation using Scheme+libgit2 vs shellout plumbing Git Simon Tournier
2023-09-12 11:07 ` Attila Lendvai
2023-09-14 10:30 ` Ludovic Courtès
2023-09-14 11:56 ` Simon Tournier
2023-09-11 17:52 ` hard dependency on Git? (was bug#65866: [PATCH 0/8] Add built-in builder for Git checkouts) Simon Tournier
2023-09-11 18:20 ` Maxim Cournoyer
2023-09-12 9:06 ` Josselin Poiret
2023-09-12 12:56 ` Maxim Cournoyer
2023-09-12 14:08 ` wolf
2023-09-14 10:22 ` Ludovic Courtès
2023-09-14 16:51 ` Ludovic Courtès
2023-09-14 17:28 ` Simon Tournier
2023-09-17 2:16 ` Maxim Cournoyer
2023-09-18 13:56 ` [bug#65866] " Ludovic Courtès
2023-09-18 14:45 ` Simon Tournier
2023-09-19 14:43 ` bug#65866: [PATCH 0/8] Add built-in builder for Git checkouts Ludovic Courtès
2023-09-19 17:09 ` Simon Tournier
2023-09-11 19:35 ` hard dependency on Git? (was bug#65866: [PATCH 0/8] Add built-in builder for Git checkouts) Vagrant Cascadian
2023-09-11 21:23 ` Csepp
2023-09-12 7:44 ` Simon Tournier
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=ZP9Tk1K37Rv8qqv2@ws \
--to=wolf@wolfsden.cz \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).