Closed
Bug 104953
Opened 25 years ago
Closed 22 years ago
installed-chrome.txt file is picky about ordering.
Categories
(SeaMonkey :: Themes, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: jelwell, Assigned: jelwell)
References
()
Details
(Keywords: platform-parity)
Attachments
(2 files)
|
1.68 KB,
patch
|
Details | Diff | Splinter Review | |
|
1.60 KB,
patch
|
peterv
:
review+
sfraser_bugs
:
superreview+
|
Details | Diff | Splinter Review |
The installed-chrome.txt file wants the skin,select,install line to be at the
bottom.
patch is coming.
| Assignee | ||
Comment 1•25 years ago
|
||
| Assignee | ||
Comment 2•25 years ago
|
||
inheriting bugscape info. cc'ing simon and jj
simon, jj: can I get an r, sr ASAP?
Comment 3•25 years ago
|
||
+ open(CHROMEFILE, ">${inst_chrome}") || die "Error: Failed to open
$inst_chrome\n";
+ print (CHROMEFILE $filecontents);
+ close(CHROMEFILE) || die "Error: Failed to close $inst_chrome\n";
+
open(CHROMEFILE, ">>${inst_chrome}") || die "Error: Failed to open
$inst_chrome\n";
print(CHROMEFILE "${chrome_entry}\n");
Why do you open the file, write to it, close it, open again in append mode, and
write again? Why not just open the file once?
| Assignee | ||
Comment 4•25 years ago
|
||
Comment 5•25 years ago
|
||
Comment on attachment 53677 [details] [diff] [review]
ok, new patch.
sr=sfraser
Attachment #53677 -
Flags: superreview+
| Assignee | ||
Comment 6•25 years ago
|
||
peterv: I hear you are an appropriate person to get an r= from for this module. :)
| Assignee | ||
Updated•25 years ago
|
Whiteboard: [OSX+][PDT] [ETA 10/15/2001] → [OSX+][PDT] [fix in hand
Comment 7•25 years ago
|
||
pls check this in for 094 = PDT+
Whiteboard: [OSX+][PDT] [fix in hand → [OSX+][PDT+] [fix in hand]
| Assignee | ||
Comment 8•25 years ago
|
||
fix checked into the branch. will apply to the trunk after i pull/rebuild there.
jj gave me an r= in an IM conversation. :)
Comment 9•25 years ago
|
||
Comment on attachment 53677 [details] [diff] [review]
ok, new patch.
>+ my $skinselect = "";
>+ my $set = 0;
Do you really need both? It seems $set == 1 is the same as $skinselect != "".
>+ print (CHROMEFILE $filecontents);
> print(CHROMEFILE "${chrome_entry}\n");
Don't add a space after print.
Only nits, r=peterv regardless.
Attachment #53677 -
Flags: review+
| Assignee | ||
Comment 10•25 years ago
|
||
pulling off PDT radar, as this is fixed on the branch. i'm working on getting a
trunk build going on my OS X machine to get this into the trunk as well.
Keywords: nsbranch+
Whiteboard: [OSX+][PDT+] [fix in hand]
Comment 11•23 years ago
|
||
Any progress on getting this in the trunk, if it is still relevant ? and
possibly the 1.3b branch?
Comment 12•22 years ago
|
||
As far as I can see, the file this was patches against does no longer exist.
Marking WFM.
Severity: blocker → normal
Status: ASSIGNED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Updated•18 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•