unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Marko Rauhamaa <marko@pacujo.net>
To: Mark H Weaver <mhw@netris.org>
Cc: Andy Wingo <wingo@pobox.com>, guix-devel@gnu.org, guile-user@gnu.org
Subject: Re: guix is the guildhall that we always wanted!
Date: Fri, 17 Mar 2017 08:51:57 +0200	[thread overview]
Message-ID: <87inn8l7jm.fsf@elektro.pacujo.net> (raw)
In-Reply-To: <87a88kanjq.fsf@netris.org> (Mark H. Weaver's message of "Thu, 16 Mar 2017 18:01:45 -0400")

Mark H Weaver <mhw@netris.org>:

> We need to keep all Guix package definitions within Guix itself, for
> the same reason that Linux (the kernel) developers insist on keeping
> all device drivers within a single monolithic tree.

I think that's one of the most unfortunate aspects of Linux.

Just saying.


Marko

  parent reply	other threads:[~2017-03-17  6:51 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-16 18:25 guix is the guildhall that we always wanted! Andy Wingo
2017-03-16 19:26 ` Amirouche Boubekki
2017-03-17  8:23   ` Andy Wingo
2017-03-18  0:10     ` Arne Babenhauserheide
2017-03-16 22:01 ` Mark H Weaver
2017-03-16 22:24   ` Ludovic Courtès
2017-03-17  9:01     ` Florian Paul Schmidt
2017-03-17  9:45       ` Andy Wingo
2017-03-17 11:24       ` Ludovic Courtès
2017-03-17  6:51   ` Marko Rauhamaa [this message]
2017-03-17  8:30   ` Andy Wingo
2017-03-17 13:54     ` Christopher Allan Webber
2017-03-17 14:26       ` Andy Wingo
2017-03-18 14:00         ` Ludovic Courtès
2017-03-17 11:30 ` Ludovic Courtès
2017-03-17 12:32   ` Andy Wingo
2017-03-17 17:39     ` Pjotr Prins
2017-03-17 18:16       ` Mike Gran
2017-03-17 13:22   ` Eli Zaretskii
2017-03-18 14:04     ` Ludovic Courtès
2017-03-18 14:10       ` Eli Zaretskii
2017-03-19 15:57         ` Ludovic Courtès
2017-03-19 16:22           ` Eli Zaretskii

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=87inn8l7jm.fsf@elektro.pacujo.net \
    --to=marko@pacujo.net \
    --cc=guile-user@gnu.org \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.org \
    --cc=wingo@pobox.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).