all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Katherine Cox-Buday <cox.katherine.e@gmail.com>
To: Andy Wingo <wingo@igalia.com>
Cc: guix-devel@gnu.org
Subject: Re: potluck status
Date: Fri, 28 Apr 2017 08:41:19 -0500	[thread overview]
Message-ID: <87inloir9c.fsf@gmail.com> (raw)
In-Reply-To: <cuc60hoenz1.fsf@igalia.com> (Andy Wingo's message of "Fri, 28 Apr 2017 14:05:54 +0200")

Andy Wingo <wingo@igalia.com> writes:

> With that I think I'd like to move to a "use" phase where I just sit
> back and see how people use the thing :)  WDYT?

I am very excited about this functionality for all of the reasons you
enumerated. I don't have any time at the moment, but I was (and still
am) interested in getting Scala and sbt packaged, and I think this is
how I would begin. I could also see packaging a few private work-related
things as potluck packages for use by myself and others.

A couple of questions:

1. When Guix grows channel support, will it have a concept of
   dev->test->prod?
2. Would it make sense for the dev channel to be expressed in terms of
   potluck packages?

I'm not very active in the community at the moment, but I wanted to
chime in and say +1, and thanks for the effort.

-- 
Katherine

  parent reply	other threads:[~2017-04-28 13:41 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-04-28 12:05 potluck status Andy Wingo
2017-04-28 12:42 ` Hartmut Goebel
2017-04-28 12:56   ` Andy Wingo
2017-04-28 16:46     ` Christopher Allan Webber
2017-04-28 19:01       ` David Pirotte
2017-05-03 13:10       ` Ludovic Courtès
2017-04-28 12:58   ` Jan Nieuwenhuizen
2017-04-28 13:12     ` Incoherent-lime
2017-04-28 13:46       ` Katherine Cox-Buday
2017-04-28 14:06         ` Incoherent-lime
2017-04-28 13:41 ` Katherine Cox-Buday [this message]
2017-04-28 14:06   ` Andy Wingo
2017-05-02  2:26     ` Katherine Cox-Buday
2017-05-02  6:58       ` Andy Wingo
2017-05-03 13:09 ` 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87inloir9c.fsf@gmail.com \
    --to=cox.katherine.e@gmail.com \
    --cc=guix-devel@gnu.org \
    --cc=wingo@igalia.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.