From owner-freebsd-questions@freebsd.org Wed Feb 24 16:35:57 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 3EBFEAB38D6 for ; Wed, 24 Feb 2016 16:35:57 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: from mail-oi0-x22b.google.com (mail-oi0-x22b.google.com [IPv6:2607:f8b0:4003:c06::22b]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (Client CN "smtp.gmail.com", Issuer "Google Internet Authority G2" (verified OK)) by mx1.freebsd.org (Postfix) with ESMTPS id EF47F197B; Wed, 24 Feb 2016 16:35:56 +0000 (UTC) (envelope-from vrwmiller@gmail.com) Received: by mail-oi0-x22b.google.com with SMTP id m82so19314255oif.1; Wed, 24 Feb 2016 08:35:56 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:cc:content-type; bh=z2i71kZCaVdPYsULHJBT1xOlby/EpB8/nQkBhpaUYR4=; b=rH6Gxug4ZNaYrL1kxjXT3NabeobRIImOtTDv+qWmtoBBYNWWi9+omg7kmn1CjjsRcq dltWMq2az1jmMpnO6AIbnRQ5RtNDvINz7cvnhL1g88DKdHlksuUnycn+JH7zartqchSd yQTAdPIc+PQw22tStWFUWpPg0pAYpfkRJ/XI7e0xfJ+APtvAuC2jw/kU1ezHKrvTxsqd KFIQ7OBWcXECtIoaBUWr5byFq4ZHvapVQ7GLssJkpAmiIOQcMR6g1ALqv/DNjN6W96ky 740zYCKlvfrheRN7Hh7gQfxoDJbWnSh/zmlEjJs+g6IhYFjsION+/blvqwF0OM/cyxQR Q1Pw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:sender:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=z2i71kZCaVdPYsULHJBT1xOlby/EpB8/nQkBhpaUYR4=; b=ce7r/AgAuF57AADaiPkc5aiHUnRXGxv1G3j6IsbVyR8fEkH0urBqtyJUnKAbIhF0nH 3M2kv5z0rv+GpM45BdvWWdrQeIBm2lgLG/oszQKcQksX7u301CxpG+gZmFRQagcj2RyB A7VKt11wcIJa3cf3O/X9Hnc0Wt62WRTZztTM2M6Gyb36xxIWSsQDWPXHau1RRl3C3ZXO ddHj0eZLW/lD081rXXl2JTWi+Q/ynM2rRCcmNcrtpsiBHDX9mycWatNi3Il6bAtUn/2u n52EWEjo3pzRaIlVdin/bS+NQyfvcLTUSdz1cESu8ygD8CBxoePK0h5Q1vTIW71s1l5e jvnw== X-Gm-Message-State: AG10YOTWFIQFDFNlKS7WN/Ep4ONBxv65Y2pqi4ShVJI4yQtZaosJRR877II8Z7hlkl5br/vq4vK5j2iTZKtUkw== MIME-Version: 1.0 X-Received: by 10.202.175.151 with SMTP id y145mr31882642oie.107.1456331756247; Wed, 24 Feb 2016 08:35:56 -0800 (PST) Sender: vrwmiller@gmail.com Received: by 10.202.226.200 with HTTP; Wed, 24 Feb 2016 08:35:56 -0800 (PST) In-Reply-To: <56CDA34A.9070906@freebsd.org> References: <56CDA34A.9070906@freebsd.org> Date: Wed, 24 Feb 2016 11:35:56 -0500 X-Google-Sender-Auth: dx-33Lu5Xx-QuhFobZqsASCMIak Message-ID: Subject: Re: Poudriere Port Options From: Rick Miller To: Matthew Seaman Cc: FreeBSD Questions Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.20 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 24 Feb 2016 16:35:57 -0000 Thanks... On Wed, Feb 24, 2016 at 7:34 AM, Matthew Seaman wrote: > On 02/24/16 11:29, Rick Miller wrote: > > I need to check what non-default port options have been set on a > Poudriere > > built repo and the options sub-command appeared to fit the bill with the > -s > > option. However, upon executing port option -s -f $file, the output > seems > > to describe what options are available along with their default setting > as > > opposed to it's current setting. Is this the expected behavior? Is > there > > an alternate method of checking what options have changed for arbitrary > > ports? > > > > poudriere options -s .... will show you the current options settings > poudriere will use when it builds anything. If you never set any > options for a particular port, then it will show you the default set of > options. > > As I recall, it's not obvious where an option has been set to anything > other than the default value. You can tell when an option has been set, > but you'll need to dig deeper to find out if the value it was set to is > different to the default. I must be crazy. Could have sworn pkg options -s displayed the default setting for an option that was known to be changed when testing it, but subsequent tests failed to prove the original assertion. You explain above that it can be determined when an option was set. Can you elaborate? It does not seem obvious (at least to me) in options.sh that this can be ascertained in this manner nor does the ports collection appear to save this to disk inside the tree, but admittedly, the only test for this was pretty rudimentary (a couple find commands). -- Take care Rick Miller