From owner-freebsd-questions@FreeBSD.ORG Fri May 25 05:56:08 2012 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 84814106564A for ; Fri, 25 May 2012 05:56:08 +0000 (UTC) (envelope-from freebsd@dreamchaser.org) Received: from nightmare.dreamchaser.org (nightmare.dreamchaser.org [12.32.44.142]) by mx1.freebsd.org (Postfix) with ESMTP id 470668FC1B for ; Fri, 25 May 2012 05:56:08 +0000 (UTC) Received: from breakaway.dreamchaser.org (breakaway.dreamchaser.org. [12.32.36.73]) by nightmare.dreamchaser.org (8.13.6/8.13.6) with ESMTP id q4P5u2w8019317; Thu, 24 May 2012 23:56:02 -0600 (MDT) (envelope-from freebsd@dreamchaser.org) Message-ID: <4FBF1EF2.5020400@dreamchaser.org> Date: Thu, 24 May 2012 23:56:02 -0600 From: Gary Aitken User-Agent: Mozilla/5.0 (X11; FreeBSD amd64; rv:12.0) Gecko/20120524 Thunderbird/12.0.1 MIME-Version: 1.0 To: Adam Vande More References: <4FBBF32D.9070505@dreamchaser.org> <20120522234510.a406941d.goksin.akdeniz@gmail.com> <4FBD7BA0.7070502@dreamchaser.org> <4FBEE05A.6000909@dreamchaser.org> <20120525035108.a3af81c1.freebsd@edvax.de> In-Reply-To: Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender IP whitelisted, not delayed by milter-greylist-2.0.2 (nightmare.dreamchaser.org [12.32.36.65]); Thu, 24 May 2012 23:56:02 -0600 (MDT) Cc: Polytropon , freebsd-questions@freebsd.org Subject: Re: automating menu options in ports (and other ports build questions) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: freebsd@dreamchaser.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 25 May 2012 05:56:08 -0000 On 05/24/12 23:34, Adam Vande More wrote: > On Thu, May 24, 2012 at 8:51 PM, Polytropon wrote: > >> On Thu, 24 May 2012 19:28:58 -0600, Gary Aitken wrote: >>> 3. Do the package builds use the defaults set in the ports tree? If >>> not, how are the options for packages chosen, and how does one determine >>> what the package options are? >> >> They use the default options. > > > This is true for most ports at least, but perhaps not true for all of them. > For example the QT4_OPTIONS controls some rather critical functionality > which is compiled into the packages however doesn't end up in a default > port install without other modification in make.conf. It > wouldn't surprise me at all if there were a few port config screens that > didn't match a package's selected options. > Is there a way to find out what options a package is built with?