Open Bug 1895251 Opened 2 years ago Updated 10 months ago

Move confvars.sh to confvars.py

Categories

(Firefox Build System :: General, task)

task

Tracking

(Not tracked)

People

(Reporter: sergesanspaille, Assigned: sergesanspaille)

References

Details

Attachments

(2 obsolete files)

confvars.sh is used to customize per-application builds, but it's scope is not clearly documented. Moving to a sandboxed python function would document the behavior, in addition to helping moving forward to the moz.configure migration.

This bounds the scope of what can be done through confvars.

One noticeable change is the removal of setting MOZ_UPDATER environment variable
in tools/update-programs/confvars, but that environment variable wasn't
honored anyway.

See Also: → 1288844
See Also: 1288844
See Also: → 1283830

This is similar to bug 1283830

Attachment #9400247 - Attachment is obsolete: true
Depends on: 1943003
Depends on: 1943009
Attachment #9459238 - Attachment is obsolete: true
Depends on: 1943300
Depends on: 1943547
Depends on: 1943612
Depends on: 1943622
Blocks: 1944245
Depends on: 1950637

This does not seem like a good change. As of 138, I'm no longer able to set MOZ_APP_UA_NAME, MOZ_APP_VENDOR, or MOZ_APP_PROFILE in branding configure.sh. I don't want to stuff this all in moz.configure as it would mean anyone doing a basic rebuild of my browser would have it show up as being from my vendor, having the UA name, and using the same profile directory which I don't want to happen.

So I think workaround set it in mozconfig, however I can't do that either. I just get a similar error "can not be set by mozconfig. Values are accepted from: implied"

Is there any way to set these without using a moz.configure file? Or do I have to just revert these changes for my fork?

Depends on: 1951143
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: