[pkg-go] Bug#801595: Bug#801595: ratt calls sbuild in a way that uses the user's sbuildrc

[Michael Stapelberg]

I’m a bit hesitant to do this. If a user specified custom settings in their
~/.sbuildrc, they are probably there for a reason and should be considered
when using ratt, right?

What speaks against asking users to set SBUILD_CONFIG= when invoking ratt?
Currently, that’d be my preferred route.

On Mon, Oct 12, 2015 at 1:19 PM, Johannes Schauer <josch at debian.org> wrote:

> Package: ratt
> Version: 0.0~git20150816.0.b060319-1
> Severity: wishlist
>
> Hi,
>
> ratt calls sbuild without setting the SBUILD_CONFIG environment variable
> which was introduced in sbuild 0.66.0-1.
>
> Without that environment variable, sbuild will use the users subildrc in
> ~/.sbuildrc which in turn might mean that the build will be carried out
> with other options than required by ratt.
>
> When using SBUILD_CONFIG you can instead specify a sane configuration
> file.
>
> On top of that you could even then add things like:
>
> $external_commands = {
>   'post-build-commands' => [
>     ['adt-run', '--changes', '%c', '--no-built-binaries', '--source',
> '%d', '---', 'schroot', 'unstable-amd64-sbuild']
>   ]
> };
>
> which would run autopkgtests as part of every build. This way, ratt
> could not only be used to check whether the reverse build dependencies
> FTBFS but would also check whether the produced binary packages pass
> their runtime tests!
>
> Thanks!
>
> cheers, josch
>
> _______________________________________________
> Pkg-go-maintainers mailing list
> Pkg-go-maintainers at lists.alioth.debian.org
> http://lists.alioth.debian.org/cgi-bin/mailman/listinfo/pkg-go-maintainers
>



-- 
Best regards,
Michael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.alioth.debian.org/pipermail/pkg-go-maintainers/attachments/20151014/ef026fde/attachment.html>