unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pierre Neidhardt <mail@ambrevar.xyz>
To: Guix-devel <guix-devel@gnu.org>, "Ludovic Courtès" <ludo@gnu.org>,
	"Pjotr Prins" <pjotr.public12@thebird.nl>
Subject: Fwd: Re: Guix & IPFS
Date: Tue, 16 Oct 2018 12:19:01 +0200	[thread overview]
Message-ID: <87zhvei48a.fsf@ambrevar.xyz> (raw)
In-Reply-To: 871s8qjjdh.fsf@ambrevar.xyz


[-- Attachment #1.1: Type: text/plain, Size: 2510 bytes --]


Re-including everyone in the conversation:

Pierre Neidhardt <mail@ambrevar.xyz> writes:

>> > Otherwise I'll just go with the first method and patch the IPFS source to use
>> > the local dependencies.
>>
>> Also fine.
>
> Hmm, on second thought, I'm not so sure.  It's a slippery slope and in the long
> run, I doubt we could easily make sure the Guix packaged dep corresponds to the
> IPFS-path dep in the source.
>
> There is a conversation upstream:
>
> 	https://github.com/ipfs/go-ipfs/issues/5054
>
> To quote one of the developers:
>
>> > We need to build IPFS downstream in Debian from reusable packaged libraries.
>> Don't do that. We havent tested and verified ipfs with those dependencies. We
>> have tested and verified ipfs with exactly the dependencies that we ship it
>> with. Building ipfs with other dependencies is just begging for something to
>> go wrong that will be super annoying for me to have to debug. If debian starts
>> shipping an ipfs built with dependencies of their choosing, my response to any
>> bug report from a debian user will be "please use a version of ipfs compiled
>> from canonical source"
>
> So I think the best idea at the moment is to write a gx-fetcher.
> It could look like the following:
>
> --8<---------------cut here---------------start------------->8---
> (define-public ipfs-go-ipfs-config
>   (let ((ipfs-hash "QmSoYrBMibm2T3LupaLuez7LPGnyrJwdRxvTfPUyCp691u"))
>     (package
>       (name "ipfs-go-ipfs-config")
>       (version (gx-version "0.2.13" revision ipfs-hash))
>       (source
>        (origin
>          (method gx-fetch)
>          (uri (gx-reference ipfs-hash))
>          (file-name (gx-file-name name version))
>          (sha256
>           (base32
>            "0qk6fshgdmhp8dip2ksm13j6nywi41m9mn0czkvmw6b697z85l2r"))))
>       (build-system go-build-system)
>       (arguments
>        '(#:unpack-path (string-append  "gx/ipfs/" ipfs-hash "/go-ipfs-config")
>          #:import-path (string-append  "gx/ipfs/" ipfs-hash "/go-ipfs-config")))
>       (home-page
>        "https://github.com/ipfs/go-ipfs-config")
>       (synopsis "...")
>       (description "...")
>       (license license:expat))))
> --8<---------------cut here---------------end--------------->8---
>
> What about a gx-build-system?  It would inherit from go-build-system and
> automate the (string-append "gx/ipfs" ...) part.  Don't know if it's worth it.


-- 
Pierre Neidhardt
https://ambrevar.xyz/

[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 487 bytes --]

  parent reply	other threads:[~2018-10-16 10:19 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-10-15  7:59 Guix & IPFS Pierre Neidhardt
2018-10-15  8:13 ` 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                   ` Pierre Neidhardt [this message]
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

  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=87zhvei48a.fsf@ambrevar.xyz \
    --to=mail@ambrevar.xyz \
    --cc=guix-devel@gnu.org \
    --cc=ludo@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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).