unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: myglc2@gmail.com
Cc: help-guix@gnu.org, Marco van Hulten <marco@hulten.org>
Subject: Re: common software
Date: Mon, 29 Jan 2018 20:14:54 +0100	[thread overview]
Message-ID: <87r2q8sci9.fsf@elephly.net> (raw)
In-Reply-To: <86372o7bkv.fsf@gmail.com>


Hi George,

> But Ludo’ what is convenient for you is not convenient for the Guix
> noob: They are most likely already using a mainstream GNU/Linux distro
> on a notebook or desktop. When they try any other distro they expect it
> to provide similar stuff to what their distro provided out of the box.
> By not doing this we a) fail to meet expectations and b) force them into
> the Guix config-o-rama, which, if we are honest, is not friendly: it's
> in scheme, far from obvious, and produces errors that helpful only to
> someone who already understands Guix.

Re errors: recently this has greatly been improved.  I’m now told that
I probably forgot to include a certain module, and how I can fix it.
Granted, simple syntax errors aren’t reported nicely, but that’s a
problem in Guile (and there’s a bug report for it).

But that’s beside the point: users who install software they need into
their user profile do not do this in the operating system configuration!
So they don’t have to touch it at all to get things like “file” or
“wget”.

I also think you’re greatly exaggerating the “unfriendliness” of Guix
configuration.

> This is why we should change the templates so that GuixSD comes OOTB
> with the same stuff as any mainstream distro. IOW, we should quickly get
> the noob running GuixSD and only then show them how cool guix-profile
> is.

Guix is all about user freedom.  Providing a bigger set of defaults
isn’t really helping, because then we’re then telling other people to
remove the packages from their configs if they don’t like them.  I much
prefer a constructive approach where you *add* what you want rather than
remove what you find was installed without your knowledge.

We already have configuration templates for different systems:
bare-bones, lightweight-desktop, and desktop.  We could add more:
audio-workstation (for common recording tools, preconfigured JACK, and
some extra kernel settings), graphics-workstation (blender, gimp,
imagemagick, etc), … But I’d leave that up to whoever feels like
maintaining and testing these templates.

--
Ricardo

GPG: BCA6 89B6 3655 3801 C3C6  2150 197A 5888 235F ACAC
https://elephly.net

  parent reply	other threads:[~2018-01-29 19:15 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-28 11:22 common software Marco van Hulten
2018-01-28 23:07 ` Ricardo Wurmus
2018-01-29 17:02   ` Ludovic Courtès
2018-01-29 18:40     ` myglc2
2018-01-29 19:14       ` zimoun
2018-01-30  0:59         ` Ricardo Wurmus
2018-01-30 10:35           ` zimoun
2018-01-31 19:05             ` pelzflorian (Florian Pelz)
2018-01-29 19:14       ` Ricardo Wurmus [this message]
2018-01-30  0:05         ` myglc2

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=87r2q8sci9.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=help-guix@gnu.org \
    --cc=marco@hulten.org \
    --cc=myglc2@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.
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).