Closed
Bug 485935
Opened 16 years ago
Closed 16 years ago
Build the default language langpack (usually en-US) as part of `make package`
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
mozilla1.9.2a1
People
(Reporter: benjamin, Assigned: benjamin)
References
Details
(Keywords: fixed1.9.1)
Attachments
(1 file)
1.64 KB,
patch
|
ted
:
review+
beltzner
:
approval1.9.1+
|
Details | Diff | Splinter Review |
From bug 485860, we should build the English langpack as part of `make package`.
Assignee | ||
Comment 1•16 years ago
|
||
Attachment #370012 -
Flags: review?(ted.mielczarek)
Comment 2•16 years ago
|
||
I'd prefer to not add an additional entry point to $(APP)/locales/Makefile.in, in particular if we're only calling it once.
Can't you just
$(MAKE) -C $(DEPTH)/browser/locales langpack_$(AB_CD) PKG_LANGPACK_PATH=
?
Updated•16 years ago
|
Assignee: l10n → nobody
Updated•16 years ago
|
Assignee: nobody → benjamin
Updated•16 years ago
|
Attachment #370012 -
Flags: review?(ted.mielczarek) → review+
Assignee | ||
Comment 4•16 years ago
|
||
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
Comment 5•16 years ago
|
||
Could we get this into 1.9.1 as well?
![]() |
||
Comment 6•16 years ago
|
||
Hmm, this is a core buildconfig bug report, but fixed with a Firefox-only patch... I filed bug 487283 to get this into the comm-central apps.
Assignee | ||
Comment 7•16 years ago
|
||
http://hg.mozilla.org/mozilla-central/rev/fcbd76b4ecf6 is a followup to this: UPLOAD_EXTRA_FILES shouldn't be prefixed with $(DIST)
Assignee | ||
Updated•16 years ago
|
Status: RESOLVED → VERIFIED
Assignee | ||
Comment 8•16 years ago
|
||
Comment on attachment 370012 [details] [diff] [review]
Package and upload the langpack by default, rev. 1
This is pretty much no-risk and gets us en-US language packs on branch, which is something localizers have requested.
Attachment #370012 -
Flags: approval1.9.1?
![]() |
||
Comment 9•16 years ago
|
||
I'm confused. Why setting PKG_LANGPACK_PATH to empty and not leave that out and just use $(LANGPACK) for UPLOAD_EXTRA_FILES?
Updated•16 years ago
|
Attachment #370012 -
Flags: approval1.9.1? → approval1.9.1+
Comment 10•16 years ago
|
||
Comment on attachment 370012 [details] [diff] [review]
Package and upload the langpack by default, rev. 1
a191=beltzner
Assignee | ||
Comment 11•16 years ago
|
||
http://hg.mozilla.org/releases/mozilla-1.9.1/rev/fbff956b7fad and langpacks are coming forth
Keywords: fixed1.9.1
Comment 12•16 years ago
|
||
During the 3.5b4 release we generated en-US.xpi and uploaded it, but it was in the wrong location. Eg dist/en-US.xpi instead of dist/linux-i686/xpi/en-US.xpi, which leads to platforms overwriting each other on ftp.m.o
Poking around in the objdir for the linux build I get
$ MOZ_PKG_PRETTYNAMES=1 make echo-variable-PKG_LANGPACK_PATH
linux-i686/xpi/
as expected. The wrong path for releases seems to be a consequence of unsetting PKG_LANGPACK_PATH in browser/installer/Makefile.in (bug 485935). We need to revisit the solution here if you want en-US for releases too.
Updated•16 years ago
|
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
![]() |
||
Comment 13•16 years ago
|
||
It's actually a bug that we even generate language packs for every platform and don't upload them into one platform-neutral directory, as language packs are supposed to be cross-platform and AFAIK, we kept them this way successfully all the time.
Assignee | ||
Comment 14•16 years ago
|
||
Comment #12-13 should be another bug if desired.
Status: REOPENED → RESOLVED
Closed: 16 years ago → 16 years ago
Resolution: --- → FIXED
Comment 15•16 years ago
|
||
Has this been done for 3.5.x release builds? If so, where can one find the en-US langpacks?
Comment 16•16 years ago
|
||
(In reply to comment #15)
> Has this been done for 3.5.x release builds? If so, where can one find the
> en-US langpacks?
>
Here is one:
ftp://ftp.mozilla.org/pub/firefox/releases/3.5.6/en-US.xpi
Updated•16 years ago
|
Target Milestone: --- → mozilla1.9.2a1
Version: unspecified → Trunk
Updated•7 years ago
|
Product: Core → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•