unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Andreas Enge <andreas@enge.fr>
To: Dirk Scheuring <scheuring@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: A secure multimedia workstation
Date: Tue, 10 Feb 2015 19:37:57 +0100	[thread overview]
Message-ID: <20150210183757.GA30353@debian> (raw)
In-Reply-To: <CALvC8ZAvM5+9Wjvzyy3Xmq9EuYV7C_6fz7n7DaT25k3iWqtPfA@mail.gmail.com>

On Tue, Feb 10, 2015 at 04:21:27PM +0100, Dirk Scheuring wrote:
> This is interesting. You seem to make packaging much easier than I
> thought it would be. I wonder why that is.

Most packages are easy, because they just require a few declarations.
One should start from easy ones, learn and move on to more complex ones.

> Moreover, there are production workflows which depend on Ardour being
> connected to other programs (5) which in turn depend on JACK. So I
> thought that I would have to track down all those interdependencies
> between programs, and include knowledge about them, libraries, etc. in
> the package receipt. I have to learn how to do that before I can
> seriously contribute, don't I?

I am not sure what you mean exactly. As Ricardo said, sometimes it is
only necessary to recursively track down the dependencies ("inputs")
of a package and then package first the ones with no inputs themselves.
And then the ones which have only inputs that you have already packaged.
And so on.

> Or am I overcomplicating things here? Thanks for any advice,

Maybe. I would suggest to start working with the Guix package manager
on top of your current system, check whether the packages we already have
satisfy your needs and start packaging the others, or file bug reports
and patches for packages that do not work as expected. It requires practice,
but not necessarily to understand everything from the start!

Andreas

  parent reply	other threads:[~2015-02-10 18:38 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-02 10:11 A secure multimedia workstation Dirk Scheuring
2015-02-05  1:24 ` 宋文武
2015-02-07 23:08 ` Ludovic Courtès
2015-02-09 17:33   ` Dirk Scheuring
2015-02-09 17:55     ` David Thompson
2015-02-09 18:23     ` Andreas Enge
2015-02-10 15:21       ` Dirk Scheuring
2015-02-10 15:45         ` Ricardo Wurmus
2015-02-10 15:56         ` Ludovic Courtès
2015-02-10 18:37         ` Andreas Enge [this message]
2015-02-11  8:25           ` Dirk Scheuring

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=20150210183757.GA30353@debian \
    --to=andreas@enge.fr \
    --cc=guix-devel@gnu.org \
    --cc=scheuring@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).