unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Yasuaki Kudo <yasu@yasuaki.com>
Cc: guix-devel@gnu.org, "Sławomir Lach" <slawek@lach.art.pl>
Subject: Re: The way to promote GUIX package manager
Date: Wed, 26 Jan 2022 23:42:05 +0100	[thread overview]
Message-ID: <87r18ui09s.fsf@elephly.net> (raw)
In-Reply-To: <AB1CBFA0-25C3-407B-8379-22E9B6AB0F90@yasuaki.com>


Yasuaki Kudo <yasu@yasuaki.com> writes:

> Does Guix really run out of the box in Debian?
>
> I have never tried it but my friend Debian expert friend keeps telling me that:
>
> * Just apt-get installing Guix doesn't work

How does “apt install guix” not work?  There’s an older version of Guix
in Debian.  After installing it “guix pull” should get the latest
version and it all works.

There’s also an installer script at https://guix.gnu.org/install.sh
which skips the detour through apt and gets you the latest release
directly.

> * and his really big complaint is evidently he creates "virtual
> environments" (short of full-on VMware, I imagine it is an assortment
> of Linux native tricks that are wrapped by tools like Docker) for
> every OS he tries but
> * Evidently the same tricks don't work with Guix

Is this not *exactly* what “guix shell” (formerly “guix enviromnent”)
does?  “guix shell -C” enters a container, even, using the same Linux
namespace mechanism that Docker wraps.

> * He does not want to try full blown Guix OS without first testing it in above ways

Guix can comfortably be used outside of Guix System.  And you can
*still* use most “guix system” commands, e.g. to build containers or
virtual machines.

-- 
Ricardo


  reply	other threads:[~2022-01-26 22:46 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26 11:09 The way to promote GUIX package manager Sławomir Lach
2022-01-26 21:38 ` Ricardo Wurmus
2022-01-26 22:40   ` Yasuaki Kudo
2022-01-26 22:42     ` Ricardo Wurmus [this message]
2022-01-26 23:15       ` Yasuaki Kudo
2022-01-27 23:35       ` Bengt Richter
2022-01-27 23:55         ` Yasuaki Kudo
2022-01-28  1:43         ` David Pirotte
2022-01-28 14:48           ` Bengt Richter
2022-01-26 23:38     ` Vagrant Cascadian
2022-02-05 13:54       ` Ludovic Courtès
2022-02-05 20:39         ` Ricardo Wurmus
2022-02-06 18:54           ` Vagrant Cascadian
2022-02-06 19:19             ` Ricardo Wurmus
2022-02-14 17:23           ` 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=87r18ui09s.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=slawek@lach.art.pl \
    --cc=yasu@yasuaki.com \
    /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).