[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Guix & IPFS

From: Ludovic Courtès
Subject: Re: Guix & IPFS
Date: Mon, 15 Oct 2018 12:21:59 +0200
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/26.1 (gnu/linux)


Pierre Neidhardt <address@hidden> skribis:

> I'm in the process of packaging IPFS.
> It has about 100 dependencies, most of which are currently missing in
> Guix, so that's gonna take me some hours :p

FWIW Pierre-Antoine (who was working with me as an intern on Guix-HPC)
has given me the last revision of the gopkg importer, which I’m planning
to include soon.  It might be useful to you!

> - IPFS is rather peculiar about its dependency versions.
> If I package all those dependencies in Guix, I should use the same
> versions.  But then we should make sure that no one is going to update
> those packages independently, which would break the strict versioning of

This seems to be the same for all Go packages: they specify the exact
commit of each of their dependencies, AIUI.

In practice it may be that upgrading will often be fine, but it does
mean that every time we upgrade a Go package, we have to build
everything “guix refresh -l GO-PACKAGE” reports to make sure.

> - gx retrieves the deps over IPFS: how important is this?  Should we do
>   the same?  What about using "gx"?  We could also implement a new
>   "gx-fetch" method fully written in Guile.

In Guix dependencies are listed statically in the ‘inputs’ fields, so I
suppose we have to run it once to retrieve that list and then “encode”
it as ‘inputs’, no?


reply via email to

[Prev in Thread] Current Thread [Next in Thread]