Closed
Bug 515862
Opened 15 years ago
Closed 15 years ago
browser.css can get out of date
Categories
(Firefox Build System :: General, defect)
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: jruderman, Unassigned)
References
Details
Attachments
(1 file)
68.68 KB,
image/png
|
Details |
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.3a1pre) Gecko/20090910 Firefox/3.7a1pre
Reporter | ||
Comment 1•15 years ago
|
||
Clobbering fixed it. My chrome://browser/skin/browser.css got out of date from my browser/themes/pinstripe/browser/browser.css. --> build config, not a bug in the patch in bug 505699
No longer blocks: 505699
Component: Toolbars → Build Config
QA Contact: toolbars → build.config
Summary: Fullscreen toolbar button is gigantic on Mac → browser.css can get out of date
Comment 2•15 years ago
|
||
I don't understand how this is possible. We rebuild the entirety of the theme any time you rebuild in browser/themes, and there are no dependencies to speak of (chrome stuff is just always rebuilt). Sounds more likely to be some local fluke than an actual problem with the build system.
Comment 3•15 years ago
|
||
Likely because of bug 468011, which would mean this is invalid.
Comment 5•15 years ago
|
||
Because it was an intentional build config change. You shouldn't have to clobber more than once.
Comment 6•15 years ago
|
||
Is the bug that old jar files are still used even though they are not intended to be part of the build? Or that the old jar files are not deleted?
Comment 7•15 years ago
|
||
I would expect that nightly users are OK because browser/installer/removed-files.in got updated, but developers with older trees would have an issue (particularly if they're using dist/bin instead of make package and dist/firefox).
Reporter | ||
Comment 8•15 years ago
|
||
I'm using e.g. ~/central/opt-obj/dist/Firefox.app/Contents/MacOS/firefox
Comment 9•15 years ago
|
||
Our build system doesn't handle blowing away the app bundle in dist, or blowing away dist/bin if things change significantly. This is why nightly/release builds are clobbers, and sometimes you just have to clobber. Removed-files.in takes care of cleaning up nightly updates, but we will never have anything in the build system that knows how to clean up files that were removed from the build. It's too much work for too little value. You'll just have to clobber on the rare occasion that this happens.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INVALID
Updated•15 years ago
|
Resolution: INVALID → WONTFIX
Assignee | ||
Updated•6 years ago
|
Component: Build Config → General
Product: Firefox → Firefox Build System
You need to log in
before you can comment on or make changes to this bug.
Description
•