Closed Bug 1453046 Opened 7 years ago Closed 7 years ago

Move SeaMonkey suite/common/ to suite/components/

Categories

(SeaMonkey :: Build Config, enhancement)

enhancement
Not set
normal

Tracking

(seamonkey2.49esr unaffected, seamonkey2.53 affected, seamonkey2.57esr fixed, seamonkey2.58 wontfix, seamonkey2.59 wontfix, seamonkey2.60 fixed)

RESOLVED FIXED
seamonkey2.60
Tracking Status
seamonkey2.49esr --- unaffected
seamonkey2.53 --- affected
seamonkey2.57esr --- fixed
seamonkey2.58 --- wontfix
seamonkey2.59 --- wontfix
seamonkey2.60 --- fixed

People

(Reporter: frg, Assigned: frg)

References

Details

Attachments

(1 file, 4 obsolete files)

Moving over common to components started in Bug 1428299. I would like to finish it before esr60 hits release. +++ This bug was initially created as a clone of Bug #1428299 +++ There are a number of areas in SeaMonkey which are unnecessarily deep, one such area is suite/profile.
Attached patch 1453046-components.patch (obsolete) — Splinter Review
Patch which moves common to components. This mostly aligns the SeaMonkey structure with Firefox and TB. No direct benefit other than that it makes locating files when porting a little easier (at least for me). There are still a few gray areas here and in mailnews which need to be sorted out later. Stefanh, rsx11m: This patch would only make sense if checked into Beta too. Otherwise we would need to rebase endlessly for ESR60. What do you think about it?
Assignee: nobody → frgrahl
Status: NEW → ASSIGNED
Attachment #8966655 - Flags: feedback?(stefanh)
Attachment #8966655 - Flags: feedback?(rsx11m.pub)
Comment on attachment 8966655 [details] [diff] [review] 1453046-components.patch >+++ b/suite/components/moz.build >+# DEFINES for preprocessing >+# Use suite/common/app-license.html as input when generating Comment needs updating I'm not happy with the amount of files sitting in the root of suite/components Do we need a suite/base/content or similar? Do we need additional sub-directories under suite/components? e.g. about, sessionstore Also files under suite/components/src and suite/components/public should be found new homes f+ as a good start but needs some fine tuning
Attachment #8966655 - Flags: feedback+
Comment on attachment 8966655 [details] [diff] [review] 1453046-components.patch In general I'm fine with that. There is a top-level common/ in comm-central already, and the distinction between suite/common and suite/components isn't quite clear to me. Thus, cleaning up potential points of confusion is certainly helpful. I'm wondering though if suite/locales/en-US/chrome/common needs corresponding modifications for consistency?
Attachment #8966655 - Flags: feedback?(rsx11m.pub) → feedback+
Attached patch 1453046-components-V2.patch (obsolete) — Splinter Review
Just a rebase to take care of the latest changes. If/When I find some time I will see if I can address the feedback and fine tune it further.
Attachment #8966655 - Attachment is obsolete: true
Attachment #8966655 - Flags: feedback?(stefanh)
Attached patch 1453046-components-V3.patch (obsolete) — Splinter Review
This should be already reviewable but I didn't test on 2.53 to see if everything works. Builds fine. I compared the comm.manifest files between comm-central and comm-esr60. There were identical and packaging also works. communicator Chrome directories also compared ok. Restored the jar.mn for sync because it is now in its own directory and not used. Deleted the obsolete nsSuiteDownloadHelper.
Attachment #8975930 - Attachment is obsolete: true
Attachment #8979050 - Flags: feedback?(iann_bugzilla)
Attached patch 1453046-components-V4.patch (obsolete) — Splinter Review
rebase after downloads was moved in Bug 888915
Attachment #8979050 - Attachment is obsolete: true
Attachment #8979050 - Flags: feedback?(iann_bugzilla)
Attachment #8983508 - Flags: review?(iann_bugzilla)
Looking at the patch I realized that common/moz.build and common/jar.mn ended mostly in base so copy and change them to retain history.
Attachment #8983508 - Attachment is obsolete: true
Attachment #8983508 - Flags: review?(iann_bugzilla)
Attachment #8983512 - Flags: review?(iann_bugzilla)
Comment on attachment 8983512 [details] [diff] [review] 1453046-components-V5.patch LGTM r=me
Attachment #8983512 - Flags: review?(iann_bugzilla) → review+
Comment on attachment 8983512 [details] [diff] [review] 1453046-components-V5.patch Given the state of the c-c tree we need it directly in esr60
Attachment #8983512 - Flags: approval-comm-esr60?
Comment on attachment 8983512 [details] [diff] [review] 1453046-components-V5.patch a=me
Attachment #8983512 - Flags: approval-comm-esr60? → approval-comm-esr60+
Pushed by frgrahl@gmx.net: https://hg.mozilla.org/comm-central/rev/0838548ddc02 Move SeaMonkey suite/common/ to suite/components/ and suite/base. r=IanN
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Pushed by frgrahl@gmx.net: https://hg.mozilla.org/comm-central/rev/58b1612f62fe Add missing new nsSessionStartup.manifest to SeaMonkey. r=me
Target Milestone: Future → seamonkey2.60
Pushed by frgrahl@gmx.net: https://hg.mozilla.org/comm-central/rev/f41b1b22aeba Remove duplicate SuiteProfileMigrator.manifest from SeaMonkey installer. r=me
This was hopefully the last problem resulting from the move. https://hg.mozilla.org/releases/comm-esr60/rev/8ac513363c1b713a631a6d8720705948f9b633dc
Blocks: 1506440
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: