Hi Geert, hi Raphael,
personally, I think that the Debian package should stop shipping
/etc/ansible/{ansible.cfg, hosts} alltogether. The reason is that those files
have a systemwide affect, and can only be edited by root. The former is
problematic if you have several projects, in that case you'd just ship a
ansible.cfg and hosts file within each project. Both those files can be edited
by the local user. For that reason I think adding debconf questions for that
is the wrong approach. But if you really want systemwide hosts and ansible
config, you can still template those with ansible. :)
What are you thoughts on this?
Greets,
Lee
On Sun, 14 Oct 2018 14:09:23 +0200 Geert Stappers <[email protected]> wrote:
>
> Found today this bugreport (
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=818008 )
> even with a patch.
>
> To find out if it stills applies there is now
> https://salsa.debian.org/stappers/ansible
> which has branch 'br818008patch'.
>
> Difference with
> https://github.com/rmedaer/ansible-debian-pkg/commit/7fa153bdcc368fad2c3dc8701fe4a8aa73c80d08
> is that updating debian/changelong is skipped. If all goes well,
> is @rmedaer the author of the commit.
>
>
> However, the question is what to do next?
>
> Would it make sense to have the patch also here in the Debian BTS?
>
> Should Ansible be configurable by debconf?
>
>
> Groeten
> Geert Stappers
> --
> Leven en laten leven
>
>
