unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: "Cook, Malcolm" <MEC@stowers.org>
Cc: Guix-devel <guix-devel@gnu.org>,
	'Pjotr Prins' <pjotr.public66@thebird.nl>,
	"'bio-packaging@mailman.open-bio.org'"
	<bio-packaging@mailman.open-bio.org>
Subject: Re: Using a shared Guix store (was RE: [Bio-packaging] testing out guix)
Date: Fri, 10 Jul 2015 10:39:10 +0200	[thread overview]
Message-ID: <87h9pce79t.fsf@gnu.org> (raw)
In-Reply-To: <1436378615368.30302@stowers.org> (Malcolm Cook's message of "Wed, 8 Jul 2015 18:03:35 +0000")

"Cook, Malcolm" <MEC@stowers.org> skribis:

>> Another one, which I think Ricardo has been investigating lately, would be to
>> have users manage their profiles via the Web user interface,
>> guix-web: <https://git.dthompson.us/guix-web.git>.  (The video
>> <http://audio-video.gnu.org/video/misc/2015-
>> 01__GNU_Guix__The_Emacs_of_Distros.webm>
>> has a demo starting at around 23mn.)
>
> Hmm, it is not clear to me how this would play out in a multi-user environment.  Having a web server that could alter per-user profiles sounds like a recipe for more confusion, rather than a solution.
>
> In any case, in my opinion, it would be a mistake to have depend on another tool (such as guix-web, or something similar) to implement functionality that could not be gained at using command-line  guix.  Don't you agree?

I’m just mentioning it as an additional option, for those who like it.

>> >> Ultimately, the correct fix is to allow remote guix clients to
>> >> communicate with a central guix daemon.  The daemon does not even
>> >> need to be aware of remote connections if guix clients can
>> >> transparently connect via SSH and send RPCs to the socket.  This is not yet
>> implemented.
>> >
>> > Sounds great.  On the roadmap?
>> 
>> Definitely.  There are details to be sorted out (SSH vs. plain old socket), but
>> we should discuss it and “get it done.”
>
> Are there any signposts on this road-map emerging?  Is there any way I can help, such as review proposals for how the CLI would work, I'd be happy to chip in.  Not ready to start slinging guile though.  Maybe later (the old lisper in me revels at the thought).

Yes, one way to help would be by trying a simple setup using Guix as it
currently exists, coupled with socat:

  http://debbugs.gnu.org/cgi/bugreport.cgi?bug=20381

If you could test this and provide feedback about the other options
discussed there, that would be great (please email
20381@debbugs.gnu.org.)

So no ETA, but once we have feedback from you, Ricardo, and other
interested parties, it will be easier to make a choice and implement it.
:-)

Thanks,
Ludo’.

  parent reply	other threads:[~2015-07-10  8:39 UTC|newest]

Thread overview: 28+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-18 20:22 Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-06-19  8:06 ` Ricardo Wurmus
2015-06-19 11:34   ` Ludovic Courtès
2015-06-25  6:40     ` Ricardo Wurmus
2015-06-19 11:40   ` Ludovic Courtès
2015-07-08 19:20     ` Cook, Malcolm
2015-07-08 19:43       ` Ricardo Wurmus
2015-06-19 17:48   ` Cook, Malcolm
2015-06-24 19:57     ` Ludovic Courtès
2015-07-08 18:03       ` Cook, Malcolm
2015-07-08 19:53         ` Ricardo Wurmus
2015-07-10  8:39         ` Ludovic Courtès [this message]
2015-07-11  0:48           ` Cook, Malcolm
2015-07-13 16:45             ` Test suite failures Ludovic Courtès
2015-07-18  3:04               ` Cook, Malcolm
2015-07-18 15:02                 ` Ludovic Courtès
2015-07-11  0:54           ` Using a shared Guix store (was RE: [Bio-packaging] testing out guix) Cook, Malcolm
2015-07-15 15:45             ` Ricardo Wurmus
2015-07-15 19:49               ` Cook, Malcolm
2015-07-15 20:28                 ` Pjotr Prins
2015-07-18  9:26                 ` Cook, Malcolm
2015-07-18 15:13                   ` Ludovic Courtès
2015-07-19  9:18                     ` Claes Wallin (韋嘉誠)
2015-07-19  9:33                       ` Andreas Enge
2015-07-20 22:37                     ` Cook, Malcolm
2015-07-21 20:23                       ` Cook, Malcolm
2015-07-21 20:29                         ` Ricardo Wurmus
2015-07-23 22:52                         ` Ludovic Courtès

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=87h9pce79t.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=MEC@stowers.org \
    --cc=bio-packaging@mailman.open-bio.org \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public66@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).