Thanks Ihar, RDO already compiles message catalogs and nothing seems affected. I also got an input from Debian maintainer (zigo) that it is a good direction in Juno. I would like to remove MO files (compiled message catalogs) in Juno when importing translations this week.
Distributions have their own packaging policy (directory hierarchy, build-depends and so on) so the detail step on how to compile message catalogs depends on distributions too. For operators who install Horizon from the source, I proposed the update of Horizon docs [1] and it can be added to the installation guide too. The way I wrote in the doc is not ideal, but I believe it is a convenient way. [1] https://review.openstack.org/#/c/126169/3/doc/source/topics/install.rst Thanks, Akihiro On Mon, Oct 6, 2014 at 8:35 PM, Ihar Hrachyshka <ihrac...@redhat.com> wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA512 > > On 04/10/14 18:12, Akihiro Motoki wrote: >> Thanks all for your input. This topic was also discussed in the >> I18N team meeting this week. >> >> All opinions I got so far are same and we seem to have a >> consensus. - not to have mo files (compile message catalogs) in our >> source git repository. - to provide a quick documentation on how to >> generate mo files and deploy them >> >> >> This consensus raises another question. At now Horizon is the only >> affected project. Is it better to apply this consensus to Juno >> Horizon release or to defer it to Kilo? One concern is that most >> distributions have already prepared packages for Kilo, so it might >> be better not to change now? I would like to know opinions from >> distributors like RDO, Debian, Ubuntu and so on. > > I was pointed (kudos to Alan Pevec) to the following update for RDO > spec file [1] that makes it regenerate MO files from source for Juno. > So for RDO, it's already handled the way we will probably go forward. > > [1]: > http://pkgs.fedoraproject.org/cgit/python-django-horizon.git/commit/?id=e756a1d0e401707d6d386516eef5c2af8ed5e138 > > /Ihar > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.22 (Darwin) > > iQEcBAEBCgAGBQJUMn5lAAoJEC5aWaUY1u570KUIAJRuxXcARheAJQB8phFlarHn > zzRNA7hA8WPBEVMRZCJjqqLKEeS/XaSN0Ue8XuR8bX4AOKA+Yh9S2X39kEWGquhI > Xdb5OqkHXPrBRAAKIdg9sPIa5SfKF9m9vEWSH84nGDczhQTeV6XBJtrnBgL9USa7 > bMmifiXg14lSNNgwwpiEkyoA1qmEsMki+yFPuvldWLvszWgl3xlTOZnY1L7auUgU > DO9bWuvSa10O463+CH4SbhhwE/k8TS3B5A/Y7eKeFwLECAHQFumgFK3bQtFE7QfB > Lv29eonr6NchEtGo+tu1W10ervDAoEVqMF6oLFtg+qF3hJwyumhH9pIV9PXVO5g= > =fkXa > -----END PGP SIGNATURE----- > > _______________________________________________ > OpenStack-dev mailing list > OpenStack-dev@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev -- Akihiro Motoki <amot...@gmail.com> _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
