From owner-freebsd-ports@FreeBSD.ORG Sat Feb 2 17:26:19 2013 Return-Path: Delivered-To: freebsd-ports@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by hub.freebsd.org (Postfix) with ESMTP id 46753E51 for ; Sat, 2 Feb 2013 17:26:19 +0000 (UTC) (envelope-from utisoft@gmail.com) Received: from mail-ie0-x22d.google.com (mail-ie0-x22d.google.com [IPv6:2607:f8b0:4001:c03::22d]) by mx1.freebsd.org (Postfix) with ESMTP id 1424FCCE for ; Sat, 2 Feb 2013 17:26:19 +0000 (UTC) Received: by mail-ie0-f173.google.com with SMTP id 9so4412321iec.4 for ; Sat, 02 Feb 2013 09:26:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:in-reply-to:references:date:message-id :subject:from:to:cc:content-type; bh=c2btDgne+m1DxFdam1OXDdOPcTy51FlKhz0TZNb+axw=; b=SYZURdeJJVP2CirwPc5ZDVk6yM3OTv5NE0g2yuFcjjfaP2HqKOldx499EanZMMgPbl /kjntTaq3tMwq/kaOELlpwXrHqEU7WzlBZdTgNAa9X9YLJvd1Jft8kEzJzoVpfXYFz1C shcVtyfx1XdFQ4mGWsRwJe8rk4J6v6I1MsezuiMYxXOshwHP/Wj+bwJrlexmUoYXKetM +tceZ6n1qpxGQnEMYWU9GVmv5dqSs3Db6048/u5eRws0vz/KBcrJfDfi+x4ES46SHZC4 ZLTaiorO0Kg/jPihCq3KBXpl9gUwGZ1PeJOzlhbM0TQRajdHL/nxK1M/d4Q5by6HGvOt umJg== MIME-Version: 1.0 X-Received: by 10.50.152.132 with SMTP id uy4mr1610240igb.62.1359825978440; Sat, 02 Feb 2013 09:26:18 -0800 (PST) Received: by 10.64.16.73 with HTTP; Sat, 2 Feb 2013 09:26:18 -0800 (PST) Received: by 10.64.16.73 with HTTP; Sat, 2 Feb 2013 09:26:18 -0800 (PST) In-Reply-To: <8C.D8.08887.13E1D015@smtp01.insight.synacor.com> References: <8C.D8.08887.13E1D015@smtp01.insight.synacor.com> Date: Sat, 2 Feb 2013 17:26:18 +0000 Message-ID: Subject: Re: security/gnupg From: Chris Rees To: Thomas Mueller Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.14 Cc: FreeBSD Mailing List X-BeenThere: freebsd-ports@freebsd.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: Porting software to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sat, 02 Feb 2013 17:26:19 -0000 On 2 Feb 2013 16:51, "Thomas Mueller" wrote: > > > > Many users have reported in the past that one of the problems with the > > ports system is that "OPTIONS" are not properly documented. Usually, if > > I spend some time, I can locate it but it is a PIA. However, with the > > "security/gnupg" port, I cannot find out specifically what this option > > does: > > > [ ] STD_SOCKET Use standard socket for agent > > > This is off by default. Is there any advantage to activating it and > > why isn't it using a standard socket to begin with? > > > Maybe if a port had a file name "options-descr" or some such thing and > > it listed each available option in the port and specifically what it > > did or how it effected the operation of the application, it would prove > > beneficial to the end use. Just my 2=A2 on the matter. > > > Jerry > > I too have the problem of options being poorly documented. I've configured a > port with two options that conflicted and only found out from the error > message when the port failed to build. > > NetBSD pkgsrc documents the options better and notes when two options are > incompatible with each other, or when exactly one of several options can or > must be chosen. > > I also find the dialog to be a nuisance because of messing the screen > especially when creating a log file. I'd like a better way of knowing what > options are available and being able to choose separately from building the > port. With NetBSD pkgsrc, options are placed in /etc/mk.conf for NetBSD and, > I believe, /usr/pkg/etc/mk.conf for other OSes. /etc/make.conf, use OPTIONS_SET=3Dlist of options. You can also use UNSET = in the same way for the converse. Setting BATCH=3Dyes stops the dialogs appearing. Chris