unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Josh Marshall <joshua.r.marshall.1991@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: How would packaging Steam-proton games be received?
Date: Thu, 31 Dec 2020 15:36:55 -0500	[thread overview]
Message-ID: <CAFkJGRd--cqC8Mp-n_PMiP3gX5zeeFaOoA8WJh4kf=gEA03H2w@mail.gmail.com> (raw)
In-Reply-To: <X+4sqNxHj/bS8HbF@jasmine.lan>

[-- Attachment #1: Type: text/plain, Size: 749 bytes --]

OK, thanks everyone.  I've got my next steps.  Sorry if this subject has
been repetitive.

On Thu, Dec 31, 2020 at 2:55 PM Leo Famulari <leo@famulari.name> wrote:

> On Thu, Dec 31, 2020 at 02:12:16PM -0500, Josh Marshall wrote:
> > So a separate channel would work for non-free software?  I know the stuff
> > is fundamentally gross.  I'd still like to have a better way to get out
> of
> > an ecosystem that is basically entirely all non-free software and a
> > transition to fully free becomes possible.
>
> Yes, channels can work for any kind of software, and they let us keep
> Guix as "100% free software". There will be occasional hiccups as the
> module imports from GNU Guix into the channel are changed, but it
> shouldn't be too often.
>

[-- Attachment #2: Type: text/html, Size: 1095 bytes --]

  reply	other threads:[~2020-12-31 20:37 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31 18:09 How would packaging Steam-proton games be received? Josh Marshall
2020-12-31 18:54 ` Christopher Baines
2020-12-31 18:56 ` Leo Famulari
2020-12-31 19:12   ` Josh Marshall
2020-12-31 19:53     ` Leo Famulari
2020-12-31 21:07       ` Leo Famulari
2021-01-09  9:47       ` Bengt Richter
2020-12-31 19:55     ` Leo Famulari
2020-12-31 20:36       ` Josh Marshall [this message]
2020-12-31 20:50       ` Ryan Prior
2020-12-31 20:55         ` Josh Marshall

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='CAFkJGRd--cqC8Mp-n_PMiP3gX5zeeFaOoA8WJh4kf=gEA03H2w@mail.gmail.com' \
    --to=joshua.r.marshall.1991@gmail.com \
    --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).