unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Hartmut Goebel <h.goebel@crazy-compilers.com>
Cc: help-guix@gnu.org
Subject: Re: string-append plus package
Date: Tue, 03 Jan 2017 00:05:48 +0100	[thread overview]
Message-ID: <87inpx6p0z.fsf@gnu.org> (raw)
In-Reply-To: <e6347b6f-5c69-5f91-8e38-0e847d30ee1b@crazy-compilers.com> (Hartmut Goebel's message of "Sun, 1 Jan 2017 16:34:33 +0100")

Hi!

Hartmut Goebel <h.goebel@crazy-compilers.com> skribis:

> To make GuixSD successful – and not just another marginal distribution –
> guix must support users and administrator to do there job. Otherwise
> they will stay with other distributions. Administrators are typically
> short in time and they are not programmes. If they are programming, they
> are used to bash, perl, python and other imperative languages. Maybe
> they have some experiences with tools like puppet or ansible, which
> introduce some declarative paradigm.

[...]

> If now guix is inconsistent to use (see below), or uses some "magic", or
> is complicated to learn, administrators will abstain from GuixSD.
>
> So the road to success is based on on simplicity, consistency and no magic.

Agreed!

> ATM, system declarations are *not* consistent: While in a package
> description (gnu/packages/*.scm) and in service definitions
> (gnu/service/*.scm) one can use "(string-append PACKAGE …)", this does

Not sure what you mean: (string-append PACKAGE STRING) never works if
PACKAGE is a package object.

> *not* work in system declarations (gnu/system/examples/*.tmpl). From an
> administrators point of view, there is no reason for this different
> behaviour. it's plain confusing.
>
> Adding on this: I took two weeks (not counting the delay caused on my
> side) to get a working answer for the simple question in this thread.
> Imagine some admin trying ot GuixSD and being delayed that long. He/she
> will just stop evaluating GuixSD.
>
> If GuixSD should become successful, you need to change this.

Agreed, except on one point: “we” instead of “you”.  It’s a
collaborative effort and no single person can “get it right” and fix
every single issue.

User experience feedback like this is crucial if we are to improve
things.

As a “fisherman” like you wrote, there are many issues that I don’t even
notice.  Reporting how the tool fails to meet your expectations like you
did is the first step towards improving it.  It may be obvious to you
that something is broken here, but it was not obvious to me until you
described your expectations.

So, thanks for helping out!

Ludo’.

  reply	other threads:[~2017-01-02 23:05 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-12-08 17:01 string-append plus package Hartmut Goebel
2016-12-08 17:28 ` Thompson, David
2016-12-08 17:46   ` Hartmut Goebel
2016-12-08 17:47     ` Thompson, David
2016-12-08 19:56 ` Leo Famulari
2016-12-19  0:13   ` Hartmut Goebel
2016-12-19  9:47     ` Ludovic Courtès
2016-12-19 11:05       ` Hartmut Goebel
2016-12-19 13:31         ` Ludovic Courtès
2017-01-01 15:34           ` Hartmut Goebel
2017-01-02 23:05             ` Ludovic Courtès [this message]
2016-12-29 10:57       ` Hartmut Goebel
2016-12-29 13:06         ` Mathieu Lirzin
2016-12-29 14:21           ` Hartmut Goebel
2016-12-30 23:42         ` Ludovic Courtès
2016-12-31 12:56           ` Hartmut Goebel
2017-01-02 23:10             ` 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=87inpx6p0z.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=h.goebel@crazy-compilers.com \
    --cc=help-guix@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.
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).