251566 - Make toolkit/ the canonical location for unforked global files (starting with l10n files)

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, defect)

Description

[Benjamin Smedberg]

As part of the l10n plan for ffox 1.0, we are coalescing all the localized files
that are part of the "new toolkit" in the toolkit/locales/(en-US) directory.

Also, as a longer-term plan, there are various modules in xpfe/ and extensions/
which are actually part of the core web-browsing experience (xpfe/appshell,
xmlextras, xslt, webservices, etc). The new toolkit requires some of these in
order to work properly (auto-update and extension management features, for
example). These files should end up living in the toolkit/ directory (keeping
the current module owners, of course).

The technical implication of this change is that developers who are building
seamonkey will need to pull the toolkit/ directory for some locale files, and
will eventually need to build parts of that directory.

Comment 1

[Benjamin Smedberg]

See http://lxr.mozilla.org/aviarybranch/source/netwerk/resources/jar.mn#7 for
how I'm keeping compatibility with seamonkey but not forking core locale files.

Comment 2

[Benjamin Smedberg]

Attachment: Everyone should pull toolkit/

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

(In reply to comment #2)
> Created an attachment (id=153300)
> Everyone should pull toolkit/

fwiw, bug 242254 has this change, too. (except the run_configure part)

Comment 4

[Benjamin Smedberg]

bryner checked in something equivalent. I would still prefer an announcement be
made about this.

Comment 5

[Benjamin Smedberg]

OK, announcement was made on npm.seamonkey and a few other NGs.

Comment 6

[Steffen Wilberg]

Comment on attachment 153300 [details] [diff] [review]
Everyone should pull toolkit/

This is obsolete then.