From mboxrd@z Thu Jan 1 00:00:00 1970 From: ng0 Subject: Re: [PATCH] gnu: Add toxic. Date: Fri, 23 Dec 2016 09:18:08 +0000 Message-ID: <87eg0zrokv.fsf@wasp.i-did-not-set--mail-host-address--so-tickle-me> References: <20161222184746.14948-1-ng0@libertad.pw> <20161222184746.14948-2-ng0@libertad.pw> <8737hfzfo1.fsf@openmailbox.org> <20161223055830.GA27511@jocasta.intra> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:52699) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1cKLzK-0000Dj-Rq for guix-devel@gnu.org; Fri, 23 Dec 2016 04:18:12 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1cKLzG-0007mP-Gx for guix-devel@gnu.org; Fri, 23 Dec 2016 04:18:06 -0500 Received: from aibo.runbox.com ([91.220.196.211]:43256) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1cKLzG-0007lr-9z for guix-devel@gnu.org; Fri, 23 Dec 2016 04:18:02 -0500 Received: from [10.9.9.212] (helo=mailfront12.runbox.com) by bars.runbox.com with esmtp (Exim 4.71) (envelope-from ) id 1cKLzE-0007qP-LA for guix-devel@gnu.org; Fri, 23 Dec 2016 10:18:00 +0100 Received: from [176.67.168.210] (helo=localhost) by mailfront12.runbox.com with esmtpsa (uid:892961 ) (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) id 1cKLzC-00081U-27 for guix-devel@gnu.org; Fri, 23 Dec 2016 10:17:58 +0100 In-Reply-To: <20161223055830.GA27511@jocasta.intra> List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: "Guix-devel" To: guix-devel@gnu.org John Darrington writes: > On Thu, Dec 22, 2016 at 06:51:10PM -0500, Kei Kebreau wrote: > ng0 writes: > > > * gnu/packages/messaging.scm (toxic): New variable. > > --- > > gnu/packages/messaging.scm | 47 ++++++++++++++++++++++++++++++++++++++++++++++ > > 1 file changed, 47 insertions(+) > > > > +(define-public toxic > > + (package > > + (name "toxic") > > + (version "0.7.2") > > + (source > > + (origin > > + (method url-fetch) > > + (uri (string-append "https://github.com/JFreegman/toxic/archive/" > > + "v" version ".tar.gz")) > > + (sha256 > > + (base32 > > + "0nbcj71ffl85l396bxc5cs8d7abn4b7absaj5asq9bvcfv52m5m2")) > > + (file-name (string-append name "-" version ".tar.gz")))) > > + (inputs > > + `(("ncurses" ,ncurses) > > I'm not sure what's up here. IIRC, we don't install the ncurses *.pc > files. If I'm wrong, someone please correct me. > > It would seem that we don't. In fact so far as I'm aware, ncurses doesn't even > provide such a thing. Instead it provides it's own pkg-config like utility called > "ncursesw60config" which you can use if you like. > > Personally however I don't like either approach. I think it much cleaner and more > reliably to explicitly state which path(s) and libraries you need rather than to > rely on some wierd script to guess it for you. > > J' > > -- > Avoid eavesdropping. Send strong encrypted email. > PGP Public key ID: 1024D/2DE827B3 > fingerprint = 8797 A26D 0854 2EAB 0285 A290 8A67 719C 2DE8 27B3 > See http://sks-keyservers.net or any PGP keyserver for public key. > I have no preference. I just have no idea right now how to fix the detection of ncurses here. If I would sit down for more than a few hours with months apart I could come up with a solution, but I'd rather use the collaborative approach and get review and ideas from other people. Kei: Thanks for solving the first part of the problem! John: If we used absolute paths for every occurence of ncurses related files in the build system of toxic, would this work? I have no time to try this at the moment. -- ♥Ⓐ ng0 | PGP keys and more: https://n0is.noblogs.org/ | http://ng0.chaosnet.org