all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Julien Lepiller <julien@lepiller.eu>
To: Jone <yeger9@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Something broke
Date: Sun, 17 Jun 2018 17:08:53 +0200	[thread overview]
Message-ID: <20180617170853.3f56c664@lepiller.eu> (raw)
In-Reply-To: <87sh5l8gv3.fsf@gmail.com>

Le Sun, 17 Jun 2018 17:25:52 +0000,
Jone <yeger9@gmail.com> a écrit :

> Hi, people! There are also prepared packages - why not a give to the
> world this? As third-patry, no warranty.
> Or is it still an experimental distro for hackers? I have prepared 3
> packages, they are not in the official delivery, but where can I send
> them? 

Hi Jone,

The ALSA_PLUGIN_DIR variable can only take one value, typically
$HOME/.guix-profile/lib/alsa-lib, where alsa and its plugins are
installed. I think guix tells you all about it when you install
alsa-lib or one of its plugins.

I'm not sure what you mean by "prepared packages", but if you mean
binaries built by someone else, we will not accept them in Guix proper.

If you've built 3 packages for Guix, we will be glad to add them to
Guix once you send them to guix-patches@gnu.org.  Please check
http://www.gnu.org/software/guix/manual/html_node/Contributing.html#Contributing
and more precisely this section:
http://www.gnu.org/software/guix/manual/html_node/Submitting-Patches.html#Submitting-Patches
to help the review process.

Thank you :)

  reply	other threads:[~2018-06-17 15:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-06-17 17:25 Something broke Jone
2018-06-17 15:08 ` Julien Lepiller [this message]
2018-06-17 15:14 ` 宋文武
  -- strict thread matches above, loose matches on Subject: below --
2018-06-17 18:56 Jone
2018-06-17 18:28 ` Julien Lepiller
2018-06-17 16:51 Jone
2018-06-17 21:37 ` Ludovic Courtès
2018-06-20 20:06   ` Jone

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=20180617170853.3f56c664@lepiller.eu \
    --to=julien@lepiller.eu \
    --cc=help-guix@gnu.org \
    --cc=yeger9@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 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.