I disagree with defining language packs in audible, because it would define
our supported language packs in two places: supported languages json file
and the new ansible script.
On Feb 14, 2014 7:46 AM, "Ben Cipollini" <notifications@github.com> wrote:

> In roles/keep/tasks/main.yml:
>
> > @@ -135,9 +135,42 @@
> >    sudo: yes
> >    sudo_user: www-data
> >
> > +# - name: Prepare directory where we build lang packs.
> > +#   git: repo=https://github.com/learningequality/ka-lite.git dest=/tmp/ka-lite-build version=release-0.11 depth=1
> > +#   sudo: yes
> > +#   tags:
> > +#     - language_packs
> > +
> > +# - name: Build the language packs.
> > +#   shell: "python /tmp/ka-lite-build/kalite/manage.py update_language_packs --ver=0.10.3"
>
> Hmmm, @jamalex <https://github.com/jamalex> can you explain why this
> would be important to do?
>
> I'm not too familiar with ansible, but language packs aren't a "system
> requirement" that can be filled by ansible. These need to be updated both
> on-demand and on a scheduled task; there's no way for ansible to determine
> whether a language pack needs updating--the scripts need to run in order to
> determine what languages need to be updated with what resources.
>
> --
> Reply to this email directly or view it on GitHub<https://github.com/fle-internal/ansible-playbooks/pull/1/files#r9752127>
> .
>