Remove options from poudriere option files for ports which were removed in the port
freebsdml at marino.st
Mon Jul 4 20:03:59 UTC 2016
On 7/4/2016 12:06, Kevin Oberman wrote:
> On Sun, Jul 3, 2016 at 5:31 PM, John Marino <freebsdml at marino.st
> <mailto:freebsdml at marino.st>> wrote:
> On 7/3/2016 19:26, John Marino wrote:
> Kimmo Paasiala <kpaasial <at> gmail.com <http://gmail.com>> writes:
> On Fri, Jul 1, 2016 at 1:17 PM, Matthias Fechner <idefix <at>
> fechner.net <http://fechner.net>> wrote:
> > Dear all,
> > it seems that poudriere can only add new options to its
> own options
> > tracking, but cannot remove options that where removed
> from the
> > of the port.
> > Concrete example is for mail/postfix
> > The option SPF was removed (2016-02-28):
> > https://www.freshports.org/mail/postfix/
> > But if I execute:
> > poudriere options -j 103amd64 -f 103amd64-pkglist
> > it will not remove the option from the options file:
> > 103amd64-options/mail_postfix/options
> > Is there a possibility to clean up all the option files
> > again at zero with:
> > poudriere options -c -j 103amd64 -f 103amd64-pkglist
> > Thanks.
> > Gruß
> > Matthias
> This is not a feature/bug of poudriere but of the ports
> system itself.
> There's no tracking of obsoleted or removed options and no
> methods to clean them up. It's only when you remove the
> options with
> 'make rmconfig' and rewrite them again trough the options
> dialog the
> obsoleted ones will be gone.
> This is incorrect. There is a clever method available to clean
> up. There is a script at Tools/scripts/redundant-opt-files.sh
> that is
> used to identify saved options that are identical to the default
> options. It also identifies option files for ports that don't
> You can remove all the obsolete and redundant options files in a
> command, e.g. "/usr/ports/Tools/scripts/redundant-opt-files.sh |
> rm -rf" which I think is pretty clever. But then again, I am
> Hmm, I may have misunderstood what Matthias was asking for. While
> Poudriere will not identify bad saved options files,
> ports-mgmt/synth will do this.
> One way to leverage this is to install synth and run "synth status
> everything" and all bad options files will be identified (printed to
> Is this new? Using synth-1.41 I get "Invalid port origin: everything".
sorry, the correct invocation is "synth status-everything". There is a
man page (man 1 synth) as well.
This email has been checked for viruses by Avast antivirus software.
More information about the freebsd-ports