Closed Bug 483996 Opened 17 years ago Closed 17 years ago

Create directory tree of all existing partner repack customizations suitable for import into hg

Categories

(Release Engineering :: General, defect)

defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: coop, Assigned: kev)

References

Details

Kev is in the process of creating this directory structure, I just wanted to get a bug on file for it. This directory structure will be checked into an hg repo for access by the build automation. I'm planning to store the script(s) used to repack builds alongside the actual partner repack config data. The complete directory structure will look something like this: partner-repacks/ partners/ google/ repack.cfg distribution/ searchplugins/ yahoo/ repack.cfg distribution/ searchplugins/ .../ scripts/ partner-repacks.py Note: I only need Kev to provide the contents of the partners/ subdir for this bug.
minor correction: partners/ partnername_1/ distribution/ distribution.ini searchplugins/ common/ plugin.xml ... locales/ <locale_1> plugin.xml ... <locale_n> plugin.xml ... partnername_n/
whoops, should be an extensions/ directory at the same level as distribution/
lets see how many spams I can add with this bug. the important directory structure is: partners/ partnername_1/ distribution/ extensions/ partner_name_2/ distribution/ extensions/ partnername_n/ distribution/ extensions/ The assumption is that the scripts would take those directories as-is and copy them to the /nonlocalized/ directory in the win32 installer, /firefox/ directory in linux-i686, and the crazy directory in OSX. k
sample repo tree is available at: people.mozilla.com:/var/www/html/files/partners/partner_repack_repo.tar.gz coop, if you need http access, let me know. it's abt 1.2MB
Thanks, Kev. I've got my script pulling builds based on the contents of your repack.cfg files now. I'll commit the whole thing to my hg user repo soon.
Status: NEW → RESOLVED
Closed: 17 years ago
Resolution: --- → FIXED
Product: mozilla.org → Release Engineering
You need to log in before you can comment on or make changes to this bug.