unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Deepan Sekar <dee93.jr@gmail.com>
Cc: guix-devel@gnu.org, gnunet-developers@gnu.org
Subject: Re: Guix - GNUnet binary distribution roadmap
Date: Fri, 21 Mar 2014 10:35:37 +0100	[thread overview]
Message-ID: <874n2r99na.fsf@gnu.org> (raw)
In-Reply-To: <CAO22TrLRVXVpDgaryawiFycOM71pFsUcbCdN1QhRk33ajVeLtw@mail.gmail.com> (Deepan Sekar's message of "Thu, 20 Mar 2014 15:53:29 +0530")

Hi, Deepan,

Deepan Sekar <dee93.jr@gmail.com> skribis:

> This is the implementation strategy(work that would be involved) I've come
> up with. If it is ok, then I'll proceed to develop the timeline for the
> work. I need your critics to improve it.

Thanks for your interest!

Note that another student, Pierre-Antoine Rault, is also interested in
this project for GSoC.  Please read the discussions we’ve had if you
haven’t already.

> 1. Users will search in the Guix store for the package. This will cause a
> Guix daemon to run which will return the installed version and the date of
> installation. This has to be worked upon.
>
> 2. Then, the user runs the command "guix get filename version_no." (new
> command which has to be implemented). This generates the hash with the
> filname and the version number as the values.

This is not the way things work in Guix.  Please read
<http://www.gnu.org/software/guix/manual/guix.html#Introduction> and
Section 2 of <http://arxiv.org/abs/1305.4584> for more info about the
hash that’s embedded in store file names.

> 3. This will in turn execute the "gnunet-dht-get" which will probe GNUnet
> DHT for the possible key/value tuples. The values will be the GNUnet peer
> which contains the file requested and the version available in the peer. A
> new implementation should be written which verifies if the version in the
> peer is greater than the existing version. This is all to be done by the
> same "gnunet-dht-get" command.
>
> 5. If so, then a MESH channel should be opened using the "gnu-mesh-connect
> gnunet_peer_id filename version". This does opening the connection,
> accessing the file and downloading the complete archive so that it
> simplifies the job for the user.
>
> 6. Once, the file has been downloaded, the implementation should verify the
> signature in the file, and call the existing guix commands to install the
> pacakage. All these features are already available. Hence, no work need to
> be done on this.

We have been refining this in the discussions with Pierre-Antoine.
Could you please start from where we left it?  I would like the proposal
to be closer to the implementation in order to avoid bad surprises
later.  In particular, see
<https://lists.gnu.org/archive/html/guix-devel/2014-03/msg00189.html>.

Thanks,
Ludo’.

_______________________________________________
GNUnet-developers mailing list
GNUnet-developers@gnu.org
https://lists.gnu.org/mailman/listinfo/gnunet-developers

  reply	other threads:[~2014-03-21  9:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-20 10:23 Guix - GNUnet binary distribution roadmap Deepan Sekar
2014-03-21  9:35 ` Ludovic Courtès [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-04-12 17:21 Deepan Sekar
2014-04-12 17:21 Deepan Sekar

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=874n2r99na.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=dee93.jr@gmail.com \
    --cc=gnunet-developers@gnu.org \
    --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 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).