all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Chris Marusich <cmmarusich@gmail.com>
To: Fis Trivial <ybbs.daans@hotmail.com>
Cc: "guix-devel@gnu.org" <guix-devel@gnu.org>
Subject: Re: Errors encountered in building guix from source.
Date: Sat, 27 Jan 2018 19:16:27 -0800	[thread overview]
Message-ID: <87a7wyhdv8.fsf@gmail.com> (raw)
In-Reply-To: <MWHPR16MB0063341575D1C01F3AE3FDF292E10@MWHPR16MB0063.namprd16.prod.outlook.com> (Fis Trivial's message of "Thu, 25 Jan 2018 20:58:38 +0000")

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

Fis Trivial <ybbs.daans@hotmail.com> writes:

> I think I will have to disable guix for a while since it's really messing
> up with my environment and I currently don't have the time to deal with
> it. :(
> I will come back latter and try joining the development for guix itself,
> really sorry.

I hope you come back soon!  Even though these kinds of things can be a
rocky road sometimes, bug reports and feedback by people like you are
essential for driving improvements in Guix.

Oleg Pykhalov <go.wigust@gmail.com> writes:

>> Can we put it in the document too? :)
>
> I don't know about how to describe it properly.  'Do not do a thing from
> guix environment' is a good for mailing list, but bad for the
> documentation, I believe.  Because the documentation should teach people
> and not give a solution.  This is why Nix discontinued their wiki site.

I feel your pain here, Fis.  I have felt the same way when I've been
bitten by specific problems with various technologies, including Guix
and Guile.  But Oleg is right: ultimately, putting specific solutions to
specific problems like this in the manual does not tend to improve the
quality of the manual.

-- 
Chris

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

      parent reply	other threads:[~2018-01-28  3:16 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-01-20 20:16 Errors encountered in building guix from source Fis Trivial
2018-01-20 20:45 ` Pjotr Prins
2018-01-21  9:13   ` Fis Trivial
2018-01-21 10:50     ` Pjotr Prins
2018-01-24 14:32 ` Ludovic Courtès
2018-01-25 15:12 ` Oleg Pykhalov
2018-01-25 20:58   ` Fis Trivial
2018-01-26 15:25     ` Oleg Pykhalov
2018-01-27 15:12       ` Fis Trivial
2018-01-29 19:20         ` Oleg Pykhalov
2018-01-29 22:35           ` Fis Trivial
2018-01-28  3:16     ` Chris Marusich [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=87a7wyhdv8.fsf@gmail.com \
    --to=cmmarusich@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=ybbs.daans@hotmail.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 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.