Re: [Engine-devel] Packaging and locales

Hi Alon, The available languages of oVirt's gwt-based portals are determined during compilation time. for run-time optimization purposes, the gwt-compiler executes a compilation-permutation per browser + per language. I assume that we can construct separate ovirt-engine[-*] packages, each one contains the gwt-based portals that were compiled only with the relevant locales (permutations). if we will do that, we won't be able to maintain all locales within the same web-application anymore (currently, the web-admin is a single web-application that supports all locales, same goes for the user-portal) - doing a separate web-application per locale probably makes more sense. also: could be trivial to do, but need to keep in mind that for every code-change, we will need to issue an update for each one of the ovirt-engine[-*] packages, and somehow make sure that the user will "yum update" *all* packages that he originally "yum install"ed, in order to avoid applications in different locales going out-of-sync. ---- Thanks, Einav ----- Original Message -----