all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: myglc2@gmail.com
To: Ricardo Wurmus <rekado@elephly.net>
Cc: help-guix@gnu.org, Marco van Hulten <marco@hulten.org>
Subject: Re: common software
Date: Mon, 29 Jan 2018 19:05:36 -0500	[thread overview]
Message-ID: <86y3kgw6r3.fsf@gmail.com> (raw)
In-Reply-To: <87r2q8sci9.fsf@elephly.net> (Ricardo Wurmus's message of "Mon, 29 Jan 2018 20:14:54 +0100")

Hi Ricardo,

On 01/29/2018 at 20:14 Ricardo Wurmus writes:

> 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).
>
Yes it has been improved.

> 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”.
>
Good point. But if they want wget to appear at startup in a user
account, adding it to system config is the only way to go, right?

> I also think you’re greatly exaggerating the “unfriendliness” of Guix
> configuration.
>
OK, I reread it. I apologize for "config-o-rama". SORRY ;-( Otherwise I
think I was being pretty objective.

>> 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.

Yes, global packages are against the Guix mantra ;-) But it is easier
for a noob to remove them than add them. So, IMO we should err on the
side of putting more in the template with comments saying, effectively,
"these are training wheels to be removed once you learn to ride Guix."

      reply	other threads:[~2018-01-30  0:05 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
2018-01-30  0:05         ` myglc2 [this message]

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86y3kgw6r3.fsf@gmail.com \
    --to=myglc2@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=marco@hulten.org \
    --cc=rekado@elephly.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.