From: ng0 <ngillmann@runbox.com>
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add epic5.
Date: Sun, 09 Oct 2016 20:51:15 +0000 [thread overview]
Message-ID: <87vax1s0u4.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <20161009194814.GA19104@jasmine>
Leo Famulari <leo@famulari.name> writes:
> On Sun, Oct 09, 2016 at 06:44:11PM +0000, ng0 wrote:
>> From: ng0 <ng0@we.make.ritual.n0.is>
>>
>> * gnu/packages/irc.scm (epic5): New variable.
>
> Thanks for the updated patch.
>
> Sorry I didn't notice this before...
>
>> + (inputs
>> + `(("openssl" ,openssl)
>> + ("ncurses" ,ncurses)
>> + ("libarchive" ,libarchive) ; CHANGELOG: "Support for loading zip files"
>> + ("perl" ,perl)
>> + ("tcl" ,tcl)
>> + ("ruby" ,ruby)
>> + ("gdbm" ,gdbm)))
>
> Using `guix gc --references $(./pre-inst-env guix build epic5)`, I
> noticed that there is no reference to gdbm.
>
> So, if you install this epic5 package and then do `guix gc`, you will
> lose gdbm and I assume that epic5 will stop working.
>
> We need to figure out a way to make sure epic5 keeps that reference.
Hm. Maybe there's an config option I can pass, if you have time to look
at it go ahead, I'll be slow and update it some time this month.
I keep poking at system services and trying to finish those, easier said
than done in some cases it turns out.
--
next prev parent reply other threads:[~2016-10-09 20:51 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-09 18:44 [PATCH] gnu: Add epic5 ng0
2016-10-09 18:44 ` ng0
2016-10-09 18:49 ` ng0
2016-10-09 19:48 ` Leo Famulari
2016-10-09 20:51 ` ng0 [this message]
2016-10-10 22:03 ` ng0
2016-12-06 19:35 ` [PATCH] v3 .. Add epic5 irc client ng0
2016-12-06 19:35 ` [PATCH] gnu: Add epic5 ng0
2016-12-08 20:38 ` Efraim Flashner
2016-12-08 21:28 ` ng0
-- strict thread matches above, loose matches on Subject: below --
2016-09-24 13:04 ng0
2016-09-25 17:13 ` Leo Famulari
2016-09-25 19:27 ` ng0
2016-10-06 22:02 ` ng0
2016-10-07 1:09 ` Leo Famulari
2016-10-09 18:14 ` 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=87vax1s0u4.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
/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).