279056 - Support extensions and themes for UMO

Status: RESOLVED INVALID

(Webtools :: Bouncer, defect)

Description

[alanjstr]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

UMO currently links directly to ftp.mozilla.org for themes and extensions hosted
on the mirrors.

We need a way for themes, extensions, plugins, sherlock plugins to be linked
through bouncer.  
ftp://ftp.mozilla.org/pub/mozilla.org/themes/708090/708090-1.49-fx.jar
would become
http://download.mozilla.org/?product=theme&name=708090&version=708090-1.49-fx.jar

This is important so that we hit the right mirrors.  

Reproducible: Always

Steps to Reproduce:

Comment 1

[Michael Morgan [:morgamic]]

In order to do this, we need to account for the absence of a language.  Would it
be possible to use en-us as the language path for these files since bouncer uses
en-us as default?

Resulting URLs would be:
ftp://ftp.mozilla.org/pub/mozilla.org/themes/708090/en-us/708090-1.49-fx.jar

Which translates to the following possible bouncer URLs:
http://download.mozilla.org/?product=theme&name=708090&version=708090-1.49-fx.jar
-or-
http://download.mozilla.org/?product=theme&name=708090&version=708090-1.49-fx.jar&lang=en-us

Comment 2

[alanjstr]

What if one file supports multiple languages?

Comment 3

[Michael Morgan [:morgamic]]

Given my proposed organization, it would fall in line with the way current
builds are handled, which bouncer is designed to handle.

Bouncer's database builds URLs consistently with file organization in the FTP
file tree:
mirror base url --> product/version --> os --> language --> filename

Or, using the code as an example:
$mirror['mirror_baseurl'].'/'.$product_version['pv_path'].'/'.$os['os_path'].'/'.$lang['lang_path'].'/'.$file['file_name']

This way, if a particular theme or extension is offered in additional language,
another filename would be added for the new language in the database (since
files are a mapping between product/version, language and OS).

Comment 4

[alanjstr]

We'll need scripts to move every item on the server and update every DB entry.  

UMO doesn't support multiple languages at all and the architecture changes
required to do so may not work well with this.  If one extension supports 10
locales, that would mean 10 XPIs would be created.  

Comment 5

[Steve Wendt]

Doesn't AMO obsolete this bug?

Comment 6

[Michael Morgan [:morgamic]]

We don't need bouncer to host .xpi's at this time.