unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Gábor Boskovits" <boskovits@gmail.com>
To: mail@ambrevar.xyz
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Guix & IPFS
Date: Mon, 15 Oct 2018 13:35:47 +0200	[thread overview]
Message-ID: <CAE4v=phLVdreFNq8uC_UwB=5J7wvHeDa0UPt5XcZBRM3+bMNxQ@mail.gmail.com> (raw)
In-Reply-To: <87lg6zjxwt.fsf@ambrevar.xyz>

Pierre Neidhardt <mail@ambrevar.xyz> ezt írta (időpont: 2018. okt.
15., H, 12:40):
>
>
> > 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!
>
> Absolutely!  Could you share the code now so that I can start using it?  Thanks!
>
> > This seems to be the same for all Go packages: they specify the exact
> > commit of each of their dependencies, AIUI.
>
> No, Go programs typically refer only to repositories, not to their commit.  This
> is precisely why it's a problem.  Golang's dependency management was not very
> well designed I'm afraid.
>

I'm not much into go, but it seems, that most of the times it is safe
to use another version of dependencies.

> Misunderstanding?
>
> > 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.
>
> Yup, but it's also the case with any other package, isn't it?
>

Sometimes it is considered safe to assume that a given update does not break
reverse dependencies, but this might lead to unexpected breakage nevertheless.
Sometimes building all revdeps are prohibitively resource consuming.

> > > - 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?
>
> Sorry, I meant "ipfs-fetch", so we might be talking about different things :p
>
> - Network: it would be nice to be able to retrieve packages over IPFS.  We can
>   do this without IPFS, just like "gx" does.
>

This seems to be orthogonal to the other issues mentioned here, and I believe it
should be implemented orthogonally (i.e. have it as an option to all,
even unrelated packages).
It would be great if integration with guix publish would be possible.

> - Importer: I don't know how Pierre-Antoine retrieves dependencies, but
>   technically it's enough to download the package and run some "go ..." command
>   to list deps.  In the case of go-ipfs (and possibly other Go packages using
>   gx), we can only list the deps with "gx deps...".  Note that in both bases the
>   package does not have to be built, if I'm not mistaken.
>
> Makes sense?
>
> --
> Pierre Neidhardt
> https://ambrevar.xyz/

  reply	other threads:[~2018-10-15 11:36 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 [this message]
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

  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='CAE4v=phLVdreFNq8uC_UwB=5J7wvHeDa0UPt5XcZBRM3+bMNxQ@mail.gmail.com' \
    --to=boskovits@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=mail@ambrevar.xyz \
    /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).