Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[Firefox] Remove unused addon l10n files (PR 9566 follow-up) #11256

Merged
merged 3 commits into from
Oct 17, 2019

Conversation

Snuffleupagus
Copy link
Collaborator

  • [Firefox] Stop building the metadata.inc/chrome.manifest.inc files during gulp locale (PR 9566 follow-up)

    With the removal of the (standalone) Firefox building code in PR Remove the Firefox extension building code. #9566 (a year and a half ago), these files are now completely unused.
    Hence it doesn't really make sense to keep building them as part of gulp locale, and the existing files in the l10n folder can also be removed (thanks to version control, they're easy enough to restore should the need ever arise).

  • [Firefox] Stop fetching the chrome.properties files during gulp importl10n (PR 9566 follow-up)

    With the removal of the (standalone) Firefox building code in PR Remove the Firefox extension building code. #9566 (a year and a half ago), these files are now completely unused in the GitHub repository[1].
    Hence it doesn't really seem necessary to keep fetching them with gulp importl10n, and the existing files in the l10n folder can also be removed (thanks to version control, they're easy enough to restore should the need ever arise).

    The patch also allows an additional simplification, for the gulp locale and gulp mozcentral commands, since it's now possible to stop writing l10n files to the extensions/firefox/ folder and instead just copy them similar to other build targets.


    [1] They're obviously still used in mozilla-central, for fallback messages displayed through PdfStreamConverter.jsm, but that doesn't make it necessary to keep them here as far as I'm concerned.

  • Update l10n files

…s during `gulp locale` (PR 9566 follow-up)

With the removal of the (standalone) Firefox building code in PR 9566 (a year and a half ago), these files are now completely unused.
Hence it doesn't really make sense to keep building them as part of `gulp locale`, and the existing files in the `l10n` folder can also be removed (thanks to version control, they're easy enough to restore should the need ever arise).
…portl10n` (PR 9566 follow-up)

With the removal of the (standalone) Firefox building code in PR 9566 (a year and a half ago), these files are now completely unused in the GitHub repository[1].
Hence it doesn't really seem necessary to keep fetching them with `gulp importl10n`, and the existing files in the `l10n` folder can also be removed (thanks to version control, they're easy enough to restore should the need ever arise).

The patch also allows an additional simplification, for the `gulp locale` and `gulp mozcentral` commands, since it's now possible to stop writing `l10n` files to the `extensions/firefox/` folder and instead just copy them similar to other build targets.

---
[1] They're obviously still used in `mozilla-central`, for fallback messages displayed through `PdfStreamConverter.jsm`, but that doesn't make it necessary to keep them *here* as far as I'm concerned.
@Snuffleupagus
Copy link
Collaborator Author

/botio-linux preview

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Received

Command cmd_preview from @Snuffleupagus received. Current queue size: 0

Live output at: http://54.67.70.0:8877/3aaf5c4ec2c062c/output.txt

@pdfjsbot
Copy link

From: Bot.io (Linux m4)


Success

Full output at http://54.67.70.0:8877/3aaf5c4ec2c062c/output.txt

Total script time: 1.62 mins

Published

@timvandermeij
Copy link
Contributor

Looks like a good change to me!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants