From owner-freebsd-ports@FreeBSD.ORG Thu Jan 15 06:27:16 2015 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id BFAA7DE3 for ; Thu, 15 Jan 2015 06:27:16 +0000 (UTC) Received: from mail-we0-x22f.google.com (mail-we0-x22f.google.com [IPv6:2a00:1450:400c:c03::22f]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id 57446E28 for ; Thu, 15 Jan 2015 06:27:16 +0000 (UTC) Received: by mail-we0-f175.google.com with SMTP id k11so12753398wes.6 for ; Wed, 14 Jan 2015 22:27:14 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=ht1Tiae+ynE5fAkSK1tYjWGNVg0GzZO7hhEZcI2jZb0=; b=tklHCGJXkkq5oCnW27d18+9bsPA/y+Iouku9x0ud5Z2W5nd1lNWr9QtvRZ2S1zJBxN dv3S+0YavkKTR0yu921Zf292+eKMfyO5ZQBLAav1PEEj1RvBs4mEjzwtI3eYLZVjiK9l 12gZk1+PniuyMCQk9RKCqREG5C3dGjgLQ+rlFeejUMknjvVQROhDrX/8EwZT+yZWmGET tsJtS5ar+/caxGTDEQxbTGZTjGsNlZcttmC4LIX5fHCd/A+FqECm3/eB/v3gB/0+F1cM vbEFun2VD94wQfehrGQH0UAzQDEKED0vbIj1UE1sqiJqwJaRUwqGaxu8V8G986U8rx8s m7pA== MIME-Version: 1.0 X-Received: by 10.194.175.7 with SMTP id bw7mr3904230wjc.107.1421303234749; Wed, 14 Jan 2015 22:27:14 -0800 (PST) Received: by 10.27.212.129 with HTTP; Wed, 14 Jan 2015 22:27:14 -0800 (PST) Date: Wed, 14 Jan 2015 22:27:14 -0800 Message-ID: Subject: postgresql93 port and libedit From: Waitman Gobble To: freebsd-ports@freebsd.org Content-Type: text/plain; charset=UTF-8 X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.18-1 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 15 Jan 2015 06:27:16 -0000 Hi, I noticed that postgresql93-client port pulls in readline, which is GPLv3. When I get rid of readline in Makefile 'USES' and also change the bottom of the Makefile in postgresql93-server, ... .include "${.CURDIR}/../postgresql92-server/Makefile" CONFIGURE_ARGS+=--with-libedit-preferred It builds without readline and links against libedit in base: # ldd /usr/local/bin/psql /usr/local/bin/psql: libpq.so.5 => /usr/local/lib/libpq.so.5 (0x800885000) libintl.so.8 => /usr/local/lib/libintl.so.8 (0x800ab3000) libssl.so.7 => /usr/lib/libssl.so.7 (0x800cbe000) libedit.so.7 => /lib/libedit.so.7 (0x800f2a000) libthr.so.3 => /lib/libthr.so.3 (0x801161000) libc.so.7 => /lib/libc.so.7 (0x801385000) libcrypto.so.7 => /lib/libcrypto.so.7 (0x80171e000) libncursesw.so.8 => /lib/libncursesw.so.8 (0x801b16000) .. there's a link to gettext libintl but that's LGPL (2.1) Anyhow I haven't done testing with psql linked to libedit instead of readline.. There's some noise about this a few years back but I don't see anything recent. Anyone have any 'bad' recent experience with libedit? pitfalls? It might be good to have libedit added as an option. I'm working on an appliance and the readline dependency kinda messes things up a bit for me. Obviously other remedies beyond ports but I think it could be a nice option. Comments appreciated. Thanks, -- Waitman Gobble Los Altos California USA 510-830-7975