all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: John Darrington <john@darrington.wattle.id.au>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org, John Darrington <jmd@gnu.org>
Subject: Re: [PATCH] gnu: pspp: Update to 0.10.0
Date: Sun, 27 Mar 2016 09:14:58 +0200	[thread overview]
Message-ID: <20160327071458.GA12887@jocasta.intra> (raw)
In-Reply-To: <20160327100004.383a9213@debian-netbook>

[-- Attachment #1: Type: text/plain, Size: 938 bytes --]

On Sun, Mar 27, 2016 at 10:00:04AM +0300, Efraim Flashner wrote:

     I pushed an update to pspp last night and I had the changes from gtk2 to
     gtk3, but I don't have the ncurses, postgresql or perl-text-diff additions.
     Are they all related to the libpq interface, and what is it?

ncurses is optional for pspp - the terminal behaviour is nicer if you have it.

perl-text-diff is not used by pspp except in its self tests.  There is one test
which needs it.  If you don't have it that test is skipped.

Postgres ships with a client interface library called libpq - using it is optional
in pspp.  If you have it, it allows pspp to directly connect to postgres databases.


J'
     

-- 
Avoid eavesdropping.  Send strong encryted 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.


[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]

  reply	other threads:[~2016-03-27  7:15 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-03-27  6:24 [PATCH] gnu: pspp: Update to 0.10.0 John Darrington
2016-03-27  7:00 ` Efraim Flashner
2016-03-27  7:14   ` John Darrington [this message]
2016-03-27 17:33     ` Ludovic Courtès
2016-03-28  7:45       ` John Darrington
2016-03-28 16:46         ` Ludovic Courtès

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=20160327071458.GA12887@jocasta.intra \
    --to=john@darrington.wattle.id.au \
    --cc=efraim@flashner.co.il \
    --cc=guix-devel@gnu.org \
    --cc=jmd@gnu.org \
    /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.