Open Bug 1427472 Opened 7 years ago Updated 2 months ago

Should --enable-official-branding really use branding/official for NIGHTLY_BUILDs?

Categories

(Firefox Build System :: General, enhancement)

enhancement

Tracking

(Not tracked)

People

(Reporter: glandium, Unassigned)

References

Details

A default build, without any specific branding option will get branding/unofficial. Which is kind of like nightly, but different. Nightly builds get branding/nightly, and Release/beta get branding/official. I'd argue --enable-official-branding, on non release/beta/esr branches should use the nightly branding. Thoughts?
Product: Core → Firefox Build System
Flags: needinfo?(mozilla)

I agree with this sentiment. We don't want anyone shipping Nightly with Firefox branding, so we should make it only possible to do deliberately by setting MOZ_OFFICIAL_BRANDING_DIRECTORY to browser/branding/official not accidentally with --enable-official-branding

Currently we switch between branding directories by just using a different variable in confvars.h

https://searchfox.org/mozilla-central/source/browser/confvars.sh#37

What's odd is we have this unnecessary check in old-configure.in:

https://searchfox.org/mozilla-central/source/old-configure.in#1398

if test -z "$MOZ_OFFICIAL_BRANDING_DIRECTORY"; then

But MOZ_OFFICIAL_BRANDING_DIRECTORY is always set by confvars.h

Flags: needinfo?(mozilla)

Well, that test comes from confvars.sh not necessarily coming from Firefox.

Q: should moz:official in search engine params return "official" on nightlies? (it currently doesn't and that seems odd) (OTOH, it seems to be only used for yahoo-jp-auctions, so the question might be, should we remove it?)

Flags: needinfo?(mozilla)
Depends on: 1747180
Depends on: 1747181

We're checking on the official thing and hopefully we'll just remove.

Flags: needinfo?(mozilla)
Depends on: 1752247
Severity: normal → S3
See Also: → 1913116
See Also: 1913116
You need to log in before you can comment on or make changes to this bug.