From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: Guix Devel <guix-devel@gnu.org>,
guix-maintainers@gnu.org, zimoun <zimon.toutoune@gmail.com>
Subject: Re: Windows Subsystem for Linux
Date: Thu, 24 Mar 2022 23:43:02 -0400 [thread overview]
Message-ID: <878rsyy9x5.fsf@gmail.com> (raw)
In-Reply-To: <87ils39hoy.fsf@gnu.org> ("Ludovic Courtès"'s message of "Thu, 24 Mar 2022 22:14:21 +0100")
Hello,
Ludovic Courtès <ludo@gnu.org> writes:
> Hi,
>
> zimoun <zimon.toutoune@gmail.com> skribis:
>
>> About FSDG, the arguments are exactly the same as GNU Emacs on
>> Windows. :-) No? I mean, GNU Emacs provides a full port on Windows and
>> such port is available on the same side as other platforms on their
>> website [1]. The rationale [2]:
>>
>> The purpose of the GNU system is to give users the freedom that
>> proprietary software takes away from its users. Proprietary
>> operating systems (like other proprietary programs) are an
>> injustice, and we aim for a world in which they do not exist.
>>
>> To improve the use of proprietary systems is a misguided
>> goal. Our aim, rather, is to eliminate them. We include support
>> for some proprietary systems in GNU Emacs in the hope that
>> running Emacs on them will give users a taste of freedom and
>> thus lead them to free themselves.
>>
>> would also make sense for GNU Guix, no?
>
> Just like the Emacs manual has an appendix on Windows support, I think
> the cookbook could have a section on setting up Guix on WSL2.
>
> Cc’ing maintainers for their thoughts!
I think if it's worded correctly (e.g., by hinting that WSL2 is an
inferior means of running Guix than via Guix System or one of the others
GNU/Linux distributions), it can be a fine and useful addition to the
cookbook. I have fellow coworkers (not at Savoir-faire Linux, mind you
:-)) who have yet to escape their Windows jail; giving them a taste of
what is possible out there with Guix would probably be a real eye
opener. At the minimum it would present Guix as a technically viable
alternative to Docker & friends in these circles.
Thanks,
Maxim
next prev parent reply other threads:[~2022-03-25 4:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-14 19:05 Building a software toolchain that works Ryan Prior
2022-03-14 20:26 ` Pjotr Prins
2022-03-14 21:40 ` David Arroyo
2022-03-15 8:19 ` Ludovic Courtès
2022-03-17 9:20 ` zimoun
2022-03-16 14:02 ` Josselin Poiret
2022-03-16 15:28 ` Ryan Prior
2022-03-16 20:13 ` Yasuaki Kudo
2022-03-17 15:35 ` Maxime Devos
2022-03-17 16:56 ` David Arroyo
2022-03-14 23:57 ` Olivier Dion via Development of GNU Guix and the GNU System distribution.
2022-03-15 8:23 ` Ludovic Courtès
2022-03-15 8:42 ` Pjotr Prins
2022-03-15 12:32 ` Yasuaki Kudo
2022-03-17 12:56 ` zimoun
2022-03-18 21:13 ` david larsson
2022-03-18 23:59 ` Yasuaki Kudo
2022-03-19 13:02 ` Windows Subsystem for Linux zimoun
2022-03-24 21:14 ` Ludovic Courtès
2022-03-25 3:43 ` Maxim Cournoyer [this message]
2022-03-25 9:04 ` Phil
2022-03-25 10:14 ` Oliver Propst
2022-03-17 20:04 ` Building a software toolchain that works Katherine Cox-Buday
2022-03-18 6:27 ` Pjotr Prins
2022-03-18 9:10 ` Oliver Propst
-- strict thread matches above, loose matches on Subject: below --
2022-03-25 14:20 Windows Subsystem for Linux Blake Shaw
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=878rsyy9x5.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=ludo@gnu.org \
--cc=zimon.toutoune@gmail.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).