From: Ricardo Wurmus <rekado@elephly.net>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH 1/2] gnu: gnunet: Add inputs.
Date: Mon, 19 Sep 2016 15:30:58 +0200 [thread overview]
Message-ID: <8737kwm2y5.fsf@elephly.net> (raw)
In-Reply-To: <20160916134921.17987-1-ng0@we.make.ritual.n0.is>
ng0 <ng0@we.make.ritual.n0.is> writes:
> * gnu/packages/gnunet.scm (gnunet)[inputs]: Add inputs
> zlib, perl, jansson, ncurses, nss, gmp, bluez, glib, libogg.
> (gnunet)[native-inputs]: Move python-2 from here ...
> to (gnunet)[inputs].
Have you checked that the resulting build artifacts retain references to
all these new inputs?
Is adding “bluez” and “libogg” really needed? They seem a little
unusual for networking software.
~~ Ricardo
next prev parent reply other threads:[~2016-09-19 13:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-16 13:49 [PATCH 1/2] gnu: gnunet: Add inputs ng0
2016-09-16 13:49 ` [PATCH 2/2] gnu: gnunet-gtk: Add gsettings-desktop-schemas to inputs ng0
2016-09-19 13:37 ` Ricardo Wurmus
2016-09-19 15:01 ` ng0
2016-09-19 13:30 ` Ricardo Wurmus [this message]
2016-09-19 14:30 ` [PATCH 1/2] gnu: gnunet: Add inputs ng0
2016-09-19 14:46 ` Ricardo Wurmus
2016-09-19 15:17 ` ng0
2016-09-19 15:21 ` Ricardo Wurmus
2016-09-19 15:34 ` Hartmut Goebel
2016-09-19 16:00 ` ng0
2016-09-19 15:37 ` ng0
2016-09-24 21:56 ` ng0
2016-09-19 15:04 ` ng0
2016-09-19 15:47 ` ng0
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=8737kwm2y5.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=ng0@we.make.ritual.n0.is \
/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).