From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Guix-devel <guix-devel@gnu.org>
Subject: Guix & IPFS
Date: Mon, 15 Oct 2018 09:59:04 +0200 [thread overview]
Message-ID: <87r2grk5dj.fsf@ambrevar.xyz> (raw)
[-- Attachment #1: Type: text/plain, Size: 1926 bytes --]
Hi Guix!
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
Thankfully Go is rather straightforward to package so that should be
alright.
That said, the case of IPFS of particular: it uses it's own dependency
manager "gx" which retrieves the specific versions of its deps over the
IFPS protocol.
The build recipe is as follows (from the project's Rules.mk):
--8<---------------cut here---------------start------------->8---
install_unsupported:
@echo "note: this command has yet to be tested to build in the system you are using"
@echo "installing gx"
go get -v -u github.com/whyrusleeping/gx
go get -v -u github.com/whyrusleeping/gx-go
@echo check gx and gx-go
gx -v && gx-go -v
@echo downloading dependencies
gx install --global
@echo "installing go-ipfs"
go install -v -tags nofuse ./cmd/ipfs
--8<---------------cut here---------------end--------------->8---
This raises a few questions:
- 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
IPFS.
Else I could package all those deps as usual (i.e. the latest version) and then for
the IPFS package I would use the native inputs as follows:
("go-path" ,(package (inherit go-path)
(version "1.1.9")
(source (origin...
(base32 <new-hash-here>)))))
I should probably define a function of PACKAGE VERSION BASE32 arguments.
- 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.
Thoughts?
--
Pierre Neidhardt
https://ambrevar.xyz/
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]
next reply other threads:[~2018-10-15 7:59 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-15 7:59 Pierre Neidhardt [this message]
2018-10-15 8:13 ` Guix & IPFS Pjotr Prins
2018-10-15 8:20 ` Pjotr Prins
2018-10-15 10:21 ` Ludovic Courtès
2018-10-15 10:40 ` Pierre Neidhardt
2018-10-15 11:35 ` Gábor Boskovits
2018-10-15 11:40 ` Pierre Neidhardt
2018-10-15 14:07 ` Pjotr Prins
2018-10-15 11:56 ` Ludovic Courtès
2018-10-15 12:56 ` Pierre Neidhardt
2018-10-15 13:56 ` Pierre Neidhardt
[not found] ` <20181015140856.xd3de5hkumtaueer@thebird.nl>
[not found] ` <8736t6jkpu.fsf@ambrevar.xyz>
[not found] ` <20181016094752.slvicfgd2rjy57u2@thebird.nl>
[not found] ` <871s8qjjdh.fsf@ambrevar.xyz>
2018-10-16 10:19 ` Fwd: " Pierre Neidhardt
2018-10-16 11:34 ` bill-auger
2018-10-16 11:44 ` Pierre Neidhardt
2018-10-16 11:51 ` Ludovic Courtès
2018-10-16 11:56 ` Pierre Neidhardt
2018-10-16 12:18 ` Pjotr Prins
2018-10-19 13:45 ` Ludovic Courtès
2018-10-16 16:27 ` Leo Famulari
2018-10-17 17:00 ` Pierre Neidhardt
2018-10-19 13:48 ` Ludovic Courtès
2018-10-19 13:56 ` Pierre Neidhardt
2018-10-23 20:18 ` Pierre Neidhardt
2018-10-24 13:17 ` Ludovic Courtès
2018-10-24 13:58 ` Pierre Neidhardt
2018-10-25 13:34 ` Ludovic Courtès
2018-10-25 17:40 ` Pierre Neidhardt
2018-10-25 19:06 ` Gábor Boskovits
2018-10-25 19:51 ` Pierre Neidhardt
2018-10-26 17:45 ` Ludovic Courtès
2018-12-09 20:19 ` Pierre Neidhardt
2018-12-10 1:52 ` Pjotr Prins
2018-12-10 8:09 ` swedebugia
2018-12-10 8:16 ` Pierre Neidhardt
2018-12-14 9:24 ` Pjotr Prins
2018-12-14 9:30 ` Pierre Neidhardt
2019-09-09 23:19 ` Pjotr Prins
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=87r2grk5dj.fsf@ambrevar.xyz \
--to=mail@ambrevar.xyz \
--cc=guix-devel@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.