From: Leo Famulari <leo@famulari.name>
To: ng0 <ngillmann@runbox.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: Add epic5.
Date: Sun, 25 Sep 2016 13:13:40 -0400 [thread overview]
Message-ID: <20160925171340.GA9499@jasmine> (raw)
In-Reply-To: <87shsp1ma8.fsf@we.make.ritual.n0.is>
[-- Attachment #1: Type: text/plain, Size: 2106 bytes --]
On Sat, Sep 24, 2016 at 01:04:47PM +0000, ng0 wrote:
> I tried to get ssl working via:
> - patching include/config.h
> - just export the variable which was in include/config.h without
> patching it.
>
> but it seems like epic5 does something different which 'justworks™' in
> ircii. epic5 is based on ircii.
> If ssl is mandatory, I'll check their git repository and see if there
> have been any commits recently fixing this.
In general, SSL / TLS support is not mandatory for packages that do
network traffic. But, users should not be misled into thinking that they
are using TLS when it doesn't work.
So, what happens when you use this epic5 to connect to an IRC server
that uses TLS?
Does it fail silently? That's not okay.
> Subject: [PATCH 1/2] licenses: Add epic.
>
> * guix/licenses.scm (epic): New variable.
Does anything else use this license? If not, I would leave it out and
use non-copyleft for the epic5 package license.
> Subject: [PATCH 2/2] gnu: Add epic5.
>
> * gnu/packages/irc.scm (epic5): New variable.
> + (add-after 'unpack 'patch-bsdinstall
> + ;; We should include this in the build-system, bsdinstall is a standard.
> + ;; If we just remove /bin/ some part of the bsdinstall breaks.
> + (lambda _
> + (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")
> + (("/etc/") ""))))
"/etc/" is not an executable path. Do we need to substitute it here?
What happens when you don't change that line?
> + (zero?
> + (system* "./configure"
> + (string-append "--prefix=" out)
> + "--with-ipv6" "--with-libarchive"
What does it use libarchive for? What happens if we leave it out?
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next prev parent reply other threads:[~2016-09-25 17:13 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 13:04 [PATCH] gnu: Add epic5 ng0
2016-09-25 17:13 ` Leo Famulari [this message]
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
-- strict thread matches above, loose matches on Subject: below --
2016-10-09 18:44 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
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
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=20160925171340.GA9499@jasmine \
--to=leo@famulari.name \
--cc=guix-devel@gnu.org \
--cc=ngillmann@runbox.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).