all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Danny Milosavljevic <dannym@scratchpost.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: 34729@debbugs.gnu.org
Subject: [bug#34729] [PATCH v2] gnu: libgit2: Avoid Python.
Date: Mon, 11 Mar 2019 23:17:02 +0100	[thread overview]
Message-ID: <20190311230424.4eea1499@scratchpost.org> (raw)
In-Reply-To: <875zspt7ls.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 1982 bytes --]

Hi Ludo,

On Mon, 11 Mar 2019 22:38:07 +0100
Ludovic Courtès <ludo@gnu.org> wrote:

> Danny Milosavljevic <dannym@scratchpost.org> skribis:
> 
> > * gnu/packages/patches/libgit2-avoid-python.patch: New file.
> > * gnu/local.mk (dist_patch_DATA): Add it.
> > * gnu/packages/version-control.scm (libgit2)[source]: Use it.
> > [inputs]: Remove python.
> > [native-inputs]: Add guile-2.2.  
> 
> So the goal is to remove Python from libgit2’s *build-time*
> dependencies, right?  (Python is not a run-time dependency for libgit2
> according to ‘guix size libgit2’.)  Can you explain a bit more?  :-)

It's listed as regular input, though (for no reason).

We use git for quite basic things in Guix (especially since we usually
use git to fetch packages from github) and we had some problems
with Python 2 (since fixed).  So Andreas, Ricardo and me looked at what
on Earth libgit2 needs Python for and found that it's just one smallish
file used at build time.

Hence the replacement :)

> This is really cool, but at the same time I feel like we’d rather have a
> compelling reason to start maintaining a parallel implementation of
> their test suite machinery.

Sure, it makes sense to think about who's going to maintain it.

In this case it's just a test case collector which basically does

$ grep -r "void.*test_" .

so I think the risk of it diverging is low.  If it after all does diverge
(and we notice it), we can always replace it by the Python version again.

It's pretty much a 1:1 port of the original (it's so long because
I made both the structure and the output the same), so it should be
easy to track future changes.

libgit2 bundled it from an upstream project, "clar".  That also usually
means that the bundled copy gets updated less often.
 
We could also try upstreaming it.

btw: I also saw that Andy once had a Python frontend for Guile, but it
appears unfinished.  Obviously that would be even nicer.

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-03-11 22:18 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04 11:04 [bug#34729] [PATCH core-updates] gnu: libgit2: Avoid Python Danny Milosavljevic
2019-03-04 11:41 ` [bug#34729] [PATCH v2 " Danny Milosavljevic
2019-03-11 21:38   ` Ludovic Courtès
2019-03-11 22:17     ` Danny Milosavljevic [this message]
2019-03-11 23:04       ` [bug#34729] [PATCH v2] " Ricardo Wurmus
2019-03-18  9:40       ` Ludovic Courtès
2019-03-18 21:31         ` Danny Milosavljevic
2019-03-21 19:07           ` Marius Bakke
2019-03-22  8:39         ` Ludovic Courtès

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=20190311230424.4eea1499@scratchpost.org \
    --to=dannym@scratchpost.org \
    --cc=34729@debbugs.gnu.org \
    --cc=ludo@gnu.org \
    /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.