From: Leo Famulari <leo@famulari.name>
To: ng0 <ng0@we.make.ritual.n0.is>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add ircii.
Date: Mon, 1 Aug 2016 20:54:13 -0400 [thread overview]
Message-ID: <20160802005413.GB15847@jasmine> (raw)
In-Reply-To: <87fuqoe10m.fsf@we.make.ritual.n0.is>
On Mon, Aug 01, 2016 at 07:34:49PM +0000, ng0 wrote:
> * gnu/packages/irc.scm (ircii): New variable.
Cool!
> + (snippet
> + '(begin
> + (substitute* "bsdinstall"
> + (("/bin/strip") "strip")
> + (("/bin/cp") "cp")
> + (("/bin/chmod") "chmod")
> + (("/etc/chown") "chown")
> + (("/bin/chgrp") "chgrp")
> + (("/bin/mkdir") "mkdir")
> + (("/bin/rm") "rm")
> + (("/bin/mv") "mv"))))))
Does anyone else think we should put this origin snippet in a build phase
instead? Or, should we leave it in the origin, where it will be applied
to the source code provided by `guix build --source ircii`?
> + (delete 'check))))
Using '#:tests? #f' is preferred instead of deleting the check phase.
> + (inputs
> + `(("libiconv" ,libiconv)
> + ("ncurses" ,ncurses)
> + ("openssl" ,openssl)))
I noticed that the built package does refer to libiconv:
---
$ guix gc --references $(./pre-inst-env guix build ircii)
/gnu/store/0kml8g9fix69v00afv59ngf4lgfr1565-openssl-1.0.2h
/gnu/store/9maps38bsia0wcxm82h0v0p2dxyn8j35-ircii-20151120
/gnu/store/9nifwk709wajpyfwa0jzaa3p6mf10vxs-gcc-4.9.3-lib
/gnu/store/m9vxvhdj691bq1f85lpflvnhcvrdilih-glibc-2.23
/gnu/store/xl19qrfzga52vrvp4ncccwjlnrjqwj95-ncurses-6.0
/gnu/store/ykzwykkvr2c80rw4l1qh3mvfdkl7jibi-bash-4.3.42
---
But, libiconv is used:
---
$ strings /gnu/store/9maps38bsia0wcxm82h0v0p2dxyn8j35-ircii-20151120/bin/irc | grep iconv
iconv_close
iconv
iconv_open
iconv_open@@GLIBC_2.2.5
iconv@@GLIBC_2.2.5
iconv_close@@GLIBC_2.2.5
---
Perhaps libiconv should be propagated?
next prev parent reply other threads:[~2016-08-02 0:54 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-01 19:34 [PATCH] gnu: Add ircii ng0
2016-08-02 0:54 ` Leo Famulari [this message]
2016-08-02 7:58 ` Andreas Enge
2016-08-02 11:30 ` ng0
2016-08-05 6:46 ` Ricardo Wurmus
2016-08-05 10:29 ` ng0
2016-08-05 11:17 ` Ricardo Wurmus
2016-08-05 12:55 ` ng0
2016-08-05 12:57 ` ng0
2016-08-05 13:01 ` ng0
2016-08-05 13:22 ` ng0
2016-08-05 15:48 ` ng0
2016-08-05 15:57 ` Leo Famulari
2016-08-05 16:11 ` ng0
2016-08-05 17:55 ` Leo Famulari
2016-08-05 18:27 ` ng0
2016-08-05 19:11 ` Leo Famulari
2016-08-09 19:38 ` Ricardo Wurmus
2016-08-09 19:47 ` Leo Famulari
2016-08-13 7:06 ` ng0
2016-08-02 12:42 ` 宋文武
2016-08-02 15:19 ` ng0
2016-08-04 19:03 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160802005413.GB15847@jasmine \
--to=leo@famulari.name \
--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 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.