Quoting Christoph Biedl (2018-07-02 18:43:52) > Thanks a lot, I'm fine with this as it's the "at least as an option" way. > Just a small thing, if I understand correctly, this change will not provide > command-line options to control the behaviour. Having these was last > refinement though as I'll use this feature in any automated setup where I > have to maintain a configuration file anyway.
At least for now I'll not add command line options for this. The number of command line options sbuild has is already very hard to read and adding six long options --lintian-require-success --no-lintian-require-success --piuparts-require-success --no-piuparts-require-success --autopkgtest-require-success --no-autopkgtest-require-success Would increase the mess even more. Plus an entry that documents each of these six options... I think we only want command line options for things that the user might want to change on a build-to-build or package-to-package basis. But for a setting like this, I expect that a user might want to either have it for everything or for nothing. If that is the case, then there is no need for a command line option. Thanks! cheers, josch
signature.asc
Description: signature
