Poudriere Port Options

Rick Miller vmiller at hostileadmin.com
Wed Feb 24 16:35:57 UTC 2016


On Wed, Feb 24, 2016 at 7:34 AM, Matthew Seaman <matthew at freebsd.org> 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

More information about the freebsd-questions mailing list