Hi, Quoting Andrea Pappacoda (2022-02-19 15:39:12) > > I have in my ~/.sbuildrc: > > > > $autopkgtest_opts = [ '--', 'schroot', '%r-%a-sbuild' ]; > > > > The %r and %a escapes expand to the current distribution and architecture. > > Thanks, this works really well! Would it be possible for sbuild to pass > these options by default when the backend is schroot? This way users > would be able to simply specify --run-autopkgtest to run tests without root > privileges.
I don't think that this would be easily possible. Whenever you let something have a default you must also provide a way to change the default. This becomes especially hairy because whichever way we implement that lets users change the default now must also be conditionalized with schroot being the backend or not. I think this is yet another sign of why sbuild running autopkgtest is a layer violation. Instead of sbuild running autopkgtest, piuparts and lintian, there should be a tool above sbuild which runs sbuild, autopkgtest, piuparts and lintian. Sbuild doing the job is just a convenience option because we don't have such a tool above sbuild yet but it would be the responsibility of that tool to find out that it can drive both sbuild and autopkgtest with schroot. I'm very hesitant about adding yet more duct tape to sbuild plus the necessary documentation plus the users that will now wonder why sbuild behaviour changed and they now have to somehow overwrite the default to restore the original functionality and so on... Thanks! cheers, josch
signature.asc
Description: signature
