Closed Bug 53999 Opened 25 years ago Closed 25 years ago

Non-jar builds get wrong chrome files sometimes

Categories

(SeaMonkey :: Build Config, defect, P2)

PowerPC
Mac System 8.5
defect

Tracking

(Not tracked)

VERIFIED FIXED

People

(Reporter: sfraser_bugs, Assigned: sfraser_bugs)

Details

(Whiteboard: [rtm++])

If you turn off the flags to use jars in the mac build scripts, the build completes, but won't run, because installed-chrome.txt contains an extra / in the paths. I have a fix.
This is a teeny change in the build scripts, and will only affect developers doing non-jar builds. The fix has to be checked in.
Status: NEW → ASSIGNED
Keywords: nsbeta3
ageed
Priority: P3 → P2
Whiteboard: [nsbeta3+]
Target Milestone: --- → M19
Fixed yesterday, branch and trunk.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
verified.
Status: RESOLVED → VERIFIED
I need to reopen this, because non-jar builds don't follow the correct file replacement strategy for commercial builds.
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
Summary: Non-jar builds don't work on Mac → Non-jar builds get wrong chrome files sometimes
Keyword fixes
Status: REOPENED → ASSIGNED
Keywords: nsbeta3rtm
Whiteboard: [nsbeta3+]
update whiteboard
Whiteboard: [rtm NEED INFO]
Index: mozilla/build/mac/MozJar.pm =================================================================== RCS file: /cvsroot/mozilla/build/mac/MozJar.pm,v retrieving revision 1.5.2.1 diff -r1.5.2.1 MozJar.pm 290,291c290,321 < # print "Aliassing $src\n to\n$dst\n"; < MakeAlias($src, $dst); # don't check errors, otherwise we fail on replacement --- > # print "Aliassing $src\n to\n$dst\n"; > if ($override) > { > unlink $dst; > MakeAlias($src, $dst); # don't check errors, otherwise we fail on replacement > } > else > { > if (-e $dst) > { > #compare dates here > my($dst_moddate) = GetFileModDate($dst); > my($file_moddate) = GetFileModDate($src); > > if ($file_moddate > $dst_moddate) > { > print "Updating older file $rel_path in $dir_name\n"; > unlink $dst; > MakeAlias($src, $dst); > } > else > { > print "File $file_jar_path in $jar_id is more recent. Not updating.\n"; > } > > } > else > { > MakeAlias($src, $dst); > } > } > This patch affects non-jar builds only. i.e. it will have NO IMPACT on release builds, and is only useful for the jar developer. warren, can you r=
Comparing this to the logic on line 162 of make-jars.pl, I think they look roughly equivalent: if (!-e $destPath || $destMtime < $srcMtime || $override) { <unlink the old and make a copy> } r=warren
scc, can you sr please?
I might have factored this code slightly differently, since |MakeAlias| is the last act of every possible code path except |$file_moddate<=$dst_moddate|. But this is clean, readable, and looks correct to me. If you have tested this and found it to work, then sr=scc.
Yes, it could be refactored, but I was following the pattern I used for files in jars above. Thanks.
rtm++
Whiteboard: [rtm NEED INFO] → [rtm++]
Fixed branch and trunk.
Status: ASSIGNED → RESOLVED
Closed: 25 years ago25 years ago
Resolution: --- → FIXED
Status: RESOLVED → VERIFIED
it's in there. verified.
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.