1688487 - Move suite/security to suite/components/security

Status: RESOLVED FIXED

(SeaMonkey :: Build Config, task)

Description

[Ian Neal]

I see no reason why SeaMonkey's security prefs should sit in suite/security they would live better under suite/components/security

Comment 1

[Robert Kaiser]

Just as a note from someone who is (nowadays) an outsider: Some years ago, we were trying to get rid of /components/ and move everything to directories outside of that structure, are things going the other way again now?

Comment 2

[Ian Neal]

(In reply to Robert Kaiser from comment #1)

Just as a note from someone who is (nowadays) an outsider: Some years ago, we were trying to get rid of /components/ and move everything to directories outside of that structure, are things going the other way again now?

Seems so :)

Comment 3

[Ian Neal]

Attachment: 1688487-security-2537.patch

[Approval Request Comment]
Regression caused by (bug #): n/a
User impact if declined: none
Testing completed (on m-c, etc.): 2.53.7
Risk to taking this patch (and alternatives if risky): none
String changes made by this patch: none

Comment 4

[Frank-Rainer Grahl (:frg)]

Comment on attachment 9198888 [details] [diff] [review]
1688487-security-2537.patch

LGTM. Thought about putting it in prefs but this would probabaly need more work.

Robert we are basically aligning with Firefox and Thunderbird here. Odd man out is usually fine but makes no sense to always search were stuff is in the other products if you need to check something :)

Comment 5

[Pulsebot]

Pushed by [e-mail]:
https://hg.mozilla.org/comm-central/rev/ed64964f05e6
Move suite/security to suite/components/security. r=frg

Comment 6

[Frank-Rainer Grahl (:frg)]

https://gitlab.com/seamonkey-project/seamonkey-2.53-comm/-/commit/3bc07da018a17834b67707a717469d732cb13e8e
Move suite/security to suite/components/security. r=frg a=frg
Target 2.53.7