unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Ricardo Wurmus <rekado@elephly.net>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org, Reshu Singh <reshusinghhh@gmail.com>
Subject: Re: Outreachy'18
Date: Tue, 06 Mar 2018 22:34:22 +0100	[thread overview]
Message-ID: <877eqonb1d.fsf@elephly.net> (raw)
In-Reply-To: <fd7470470946972cacf545cb0ccf2754@tobias.gr>


Hi Tobias,

> That said, you should consider installing Guix manually using the
> guide above, instead of using a script:
>
> - The installation script is still quite new and probably won't work
> in all cases.
> - Error reporting is primitive, as you've experienced, which makes it
> hard for us to help.
> - Manually installing isn't *that* difficult, and most importantly:
> - Understanding the concepts involved will serve as a valuable
> introduction to hacking on Guix.

These are good points.

I should clarify that I suggested to Reshu to use the script to get
started a little more quickly.  This is for making a first recorded
contribution, which is a requirement for all who want to become an
Outreachy intern.

--
Ricardo

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

  parent reply	other threads:[~2018-03-06 21:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-06 19:34 Outreachy'18 Reshu Singh
2018-03-06 20:06 ` Outreachy'18 Konrad Hinsen
2018-03-06 20:28   ` Outreachy'18 Ricardo Wurmus
2018-03-06 20:54   ` Outreachy'18 Tobias Geerinckx-Rice
2018-03-06 20:59     ` Outreachy'18 Tobias Geerinckx-Rice
2018-03-06 21:34     ` Ricardo Wurmus [this message]
2018-03-07  4:02       ` Outreachy'18 Reshu Singh
2018-03-06 20:32 ` Outreachy'18 Ricardo Wurmus
2018-03-06 21:00   ` Outreachy'18 Gábor Boskovits
2018-03-06 21:16 ` Outreachy'18 Clément Lassieur

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=877eqonb1d.fsf@elephly.net \
    --to=rekado@elephly.net \
    --cc=guix-devel@gnu.org \
    --cc=me@tobias.gr \
    --cc=reshusinghhh@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).