Changes between Initial Version and Version 1 of Ticket #27466, comment 9


Ignore:
Timestamp:
Feb 8, 2019, 4:10:01 PM (8 months ago)
Author:
intrigeri
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #27466, comment 9

    initial v1  
    22> This seems to be requiring mercurial and not git to get the l10n sources. I wonder if we could cheat here (or do the whole transition in a multi-step approach) and use the downloaded and verified language packs pointing the repackaging machinery to the unzipped strings instead of a mercurial repo...
    33
    4 This is actually not a problem. We are about to do this for the mobile multi language bundle (see: #26483). In fact, looking at the related documentation there should be an option available to provide such a one-bundle-including-all-locale for desktop as well. However, I think we should not make that move for our desktop platforms but rather stick to what Mozilla does, which is the topic of this bug.
     4This is actually not a problem. We are about to do this for the mobile multi language bundle (see: #26843). In fact, looking at the related documentation there should be an option available to provide such a one-bundle-including-all-locale for desktop as well. However, I think we should not make that move for our desktop platforms but rather stick to what Mozilla does, which is the topic of this bug.
    55
    66The repackaging is happening during the regular Firefox build and the logic around it is quite complex. So, I am still thinking about how to do this best in our reproducible builds setup. Exporting all the neceassary tools and doing the rebundling in the `tor-browser` step (where we are currently kind of rebundling by adding our own search engines etc.) is likely not easily feasible.