all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Thompson, David" <dthompson2@worcester.edu>
To: Pjotr Prins <pjotr.public12@thebird.nl>
Cc: guix-devel <guix-devel@gnu.org>
Subject: Re: More INSTALL and HACKING docs
Date: Sat, 13 Jun 2015 08:29:01 -0400	[thread overview]
Message-ID: <CAJ=Rwfai87ZvFEXGx9EuztWsiGsmRVMgpGCdYDR_OHCzodnVeA@mail.gmail.com> (raw)
In-Reply-To: <20150613114307.GA8949@thebird.nl>

On Sat, Jun 13, 2015 at 7:43 AM, Pjotr Prins <pjotr.public12@thebird.nl> wrote:
> Because I don't trust my memory I tend to write up what I find out
>
>   https://github.com/pjotrp/guix-notes/blob/master/INSTALL.org
>   https://github.com/pjotrp/guix-notes/blob/master/HACKING.org
>
> Malcolm also started one
>
>   https://github.com/malcook/sce/blob/master/README.org
>
> since it is written in Org-mode, we hope some of it might find its way
> into the main docs eventually.
>
> Corrections appreciated!!

Hey, this is good stuff!  I like how some explanations are framed from
a Rubyists perspective.  I hope it may help some Ruby programmers join
in on all the packaging fun.

I would like to correct something in the HACKING.org document:

    Note that Docker is a propriety technology and frowned upon by
members of the GNU Guix community.

Docker is free software[0].  Some of us may not be very enthusiastic
about Docker (me), but we do not frown upon it because it gives its
users the 4 freedoms.  I also feel that this is a good time to mention
that someone should package the Go compiler. ;)

Thanks,

- Dave

[0] https://github.com/docker/docker

      reply	other threads:[~2015-06-13 12:29 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-13 11:43 More INSTALL and HACKING docs Pjotr Prins
2015-06-13 12:29 ` Thompson, David [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='CAJ=Rwfai87ZvFEXGx9EuztWsiGsmRVMgpGCdYDR_OHCzodnVeA@mail.gmail.com' \
    --to=dthompson2@worcester.edu \
    --cc=guix-devel@gnu.org \
    --cc=pjotr.public12@thebird.nl \
    /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.