Closed
Bug 1361370
Opened 7 years ago
Closed 7 years ago
It is not possible to override the values of MOZ_SOURCE_CHANGESET and MOZ_SOURCE-REPO in Seamonkey builds
Categories
(SeaMonkey :: General, defect)
SeaMonkey
General
Tracking
(Not tracked)
RESOLVED
FIXED
seamonkey2.52
People
(Reporter: wgianopoulos, Assigned: wgianopoulos)
References
Details
(Keywords: regression)
Attachments
(1 file, 3 obsolete files)
1.59 KB,
patch
|
glandium
:
review+
|
Details | Diff | Splinter Review |
For a Frefox build it si possible to override the values for MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO for a custom build by defining these vaues in system environment variables. In fact the Seamonkey build makes use of this feature to ensure that about:buildconfig reflects the Seamonkey repository and changeset rather than the gecko ones. Unfortunately, it does this in an unconditional manner. It should only be defining these environment variables if they are not already defined, to permit the builder to override these values.
Assignee | ||
Updated•7 years ago
|
Blocks: 1267270
Keywords: regression
Assignee | ||
Comment 1•7 years ago
|
||
Attachment #8863752 -
Flags: review?(aleth)
Assignee | ||
Comment 2•7 years ago
|
||
Ooops had wrong reviewer and not really a checkin ready comment.
Attachment #8863763 -
Flags: review?(mh+mozilla)
Assignee | ||
Updated•7 years ago
|
Attachment #8863752 -
Attachment is obsolete: true
Attachment #8863752 -
Flags: review?(aleth)
Assignee | ||
Comment 3•7 years ago
|
||
To make it clear why I do that, with this fix I can make about:buildconfig show the comm-central changeset my build was based from and also have a link to my build page which documents the additional patches I includue in my builds.
Assignee | ||
Comment 4•7 years ago
|
||
I accomplish this by including the following in my build script: export MOZ_INCLUDE_SOURCE_INFO=1 export MOZ_SOURCE_CHANGESET=`cat .changeset` export MOZ_SOURCE_REPO=https://hg.mozilla.org/comm-central the .changset file contains the changset from before my patches were applied.
Assignee | ||
Comment 5•7 years ago
|
||
I suppose maybe is should have also updated the comment but looking for a rview first. I was thinking perhaps changing the comment to: # Ensure the comm-* values are used unless overridden via environment variables.].
Assignee | ||
Comment 6•7 years ago
|
||
I suppose maybe is should have also updated the comment but looking for a rview first. I was thinking perhaps changing the comment to: # Ensure the comm-* values are used unless overridden via environment variables.(In reply to Bill Gianopoulos [:WG9s] from comment #5) > I suppose maybe is should have also updated the comment but looking for a > rview first. > > I was thinking perhaps changing the comment to: > > # Ensure the comm-* values are used unless overridden via environment > variables.].
Assignee | ||
Comment 7•7 years ago
|
||
Attachment #8863763 -
Attachment is obsolete: true
Attachment #8863763 -
Flags: review?(mh+mozilla)
Attachment #8863917 -
Flags: review?(mh+mozilla)
Assignee | ||
Comment 8•7 years ago
|
||
I decided to fix the comments before review.
Assignee | ||
Comment 9•7 years ago
|
||
Same patch just a typo in the comment corrected.
Attachment #8863917 -
Attachment is obsolete: true
Attachment #8863917 -
Flags: review?(mh+mozilla)
Attachment #8864811 -
Flags: review?(mh+mozilla)
Comment 10•7 years ago
|
||
Comment on attachment 8864811 [details] [diff] [review] Allow overrride of MOZ_SOURCE_CHANGESET and MOZ_SOURCE_REPO. Review of attachment 8864811 [details] [diff] [review]: ----------------------------------------------------------------- Beware that as of bug 1279048, those variables are used for debug symbol files.
Attachment #8864811 -
Flags: review?(mh+mozilla) → review+
Assignee | ||
Updated•7 years ago
|
Assignee | ||
Comment 11•7 years ago
|
||
OK so I don;t know, does adding checkin-needed as a keyword here help to get it checked in, or do I need to find my own friend with check-in privs to do this for me?
Comment 12•7 years ago
|
||
Jorg, the patch got r+ from Mike. Should I just check it in or do you want to do it?
Flags: needinfo?(jorgk)
Comment 13•7 years ago
|
||
I'll check it in when I next need a patch, so within the next 24 hours. I'll leave the NI to remind me.
Assignee | ||
Comment 14•7 years ago
|
||
(In reply to Jorg K (GMT+2) from comment #13) > I'll check it in when I next need a patch, so within the next 24 hours. I'll > leave the NI to remind me. Thanks!
Comment 15•7 years ago
|
||
https://hg.mozilla.org/comm-central/rev/bd34d80df5ff4929617aaede1ec44230f54d65f7 I quite aggressively manage C-C these days, that means, I do an C-C push after every M-C merge to detect bustage. Small patches like this one help me with that. However, at times a small patch has to wait until I need to do a push again and don't have more important patches.
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Flags: needinfo?(jorgk)
Keywords: checkin-needed
Resolution: --- → FIXED
Target Milestone: --- → seamonkey2.52
You need to log in
before you can comment on or make changes to this bug.
Description
•