--print-uninst and --nuninst-cache are not mutually-exclusive

This check has been present for a long time but there is no reason for it -
there is code elsewhere that explicitly checks for both options being set
together and DTRT.  And this saves a minute on each britney run to not
regenerate uninstallability information that was just generated.
less-recipients
Steve Langasek 3 years ago
parent 82fad57aa9
commit a7b58b76e6

@ -446,11 +446,8 @@ class Britney(object):
pass pass
# integrity checks # integrity checks
if self.options.nuninst_cache and self.options.print_uninst: # pragma: no cover
self.logger.error("nuninst_cache and print_uninst are mutually exclusive!")
sys.exit(1)
# if the configuration file exists, then read it and set the additional options # if the configuration file exists, then read it and set the additional options
elif not os.path.isfile(self.options.config): # pragma: no cover if not os.path.isfile(self.options.config): # pragma: no cover
self.logger.error("Unable to read the configuration file (%s), exiting!", self.options.config) self.logger.error("Unable to read the configuration file (%s), exiting!", self.options.config)
sys.exit(1) sys.exit(1)

Loading…
Cancel
Save