Thomas, +1
I don't know anything about the background here, but for what it's worth, I work with a team that packages RPMs for the core components (nova, keystone, etc) and we only compile the mo's at rpmbuild time, nothing binary is stored in git, only the .po files (which are converted to .mo's using babel compile_catalog). Thanks, MATT RIEDEMANN Advisory Software Engineer Cloud Solutions and OpenStack Development Phone: 1-507-253-7622 | Mobile: 1-507-990-1889 E-mail: mrie...@us.ibm.com 3605 Hwy 52 N Rochester, MN 55901-1407 United States From: Thomas Goirand <z...@debian.org> To: OpenStack Development Mailing List <OpenStack-dev@lists.openstack.org>, Date: 07/01/2013 12:29 PM Subject: [openstack-dev] [horizon] Removing the .mo files from Horizon git Hi, Is there any reason why the .mo files of Horizon are included in the Git? IMO, they have nothing to do there. They take time to download, and are the major causes of "git merge" failures for me when preparing Havana packages. Removing the .mo files would also be a good step to make sure we follow the guidelines of Debian (as binary generated files could be considered non-free, and we should make sure everything is built from source). So, shouldn't the .mo files be generated at build time only, and be kept out of the Git? Cheers, Thomas Goirand (zigo) _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
<<image/gif>>
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev