From: Yasuaki Kudo <yasu@yasuaki.com>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, "Sławomir Lach" <slawek@lach.art.pl>
Subject: Re: The way to promote GUIX package manager
Date: Thu, 27 Jan 2022 07:40:56 +0900 [thread overview]
Message-ID: <AB1CBFA0-25C3-407B-8379-22E9B6AB0F90@yasuaki.com> (raw)
In-Reply-To: <878rv2jhqn.fsf@elephly.net>
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
* 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
* He does not want to try full blown Guix OS without first testing it in above ways
* He is very comfortable with Debian - doesn't see any benefit that Guix brings
I cannot comment much because the whole point of my using Guix is precisely because I know very little if Linux and its surrounding toolset so I want to abstract it, paper it over with Guix 😄
-Yasu
> On Jan 27, 2022, at 06:43, Ricardo Wurmus <rekado@elephly.net> wrote:
>
>
> Sławomir Lach <slawek@lach.art.pl> writes:
>
>> Solution is simple:
>> 1. Keep older packages in GUIX repo, so developers could request older version
>> in scripts
>
> Unforunately, it’s really not that simply to keep older packages around.
> I’m maintaining packages for a bunch of bioinformatics tools, for
> example, which are stuck in the past. Building them becomes more and
> more difficult as time passes and the rest of the world moves on. It is
> not feasible to maintain an ever-growing collection of outdated software
> and their toolchains.
>
> But: Guix supports channels, so people who absolutely must use GCC 3 to
> build their abandoned tools to build their old source code that’s stuck
> in the past can totally do that.
>
>> Minus: possible security hell.
>
> :)
>
> --
> Ricardo
>
next prev parent reply other threads:[~2022-01-26 22:41 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 [this message]
2022-01-26 22:42 ` Ricardo Wurmus
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=AB1CBFA0-25C3-407B-8379-22E9B6AB0F90@yasuaki.com \
--to=yasu@yasuaki.com \
--cc=guix-devel@gnu.org \
--cc=rekado@elephly.net \
--cc=slawek@lach.art.pl \
/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).