Last Comment Bug 378647 - Get profile roaming working in suiterunner builds (extensions/sroaming)
: Get profile roaming working in suiterunner builds (extensions/sroaming)
: helpwanted
Product: SeaMonkey
Classification: Client Software
Component: General (show other bugs)
: Trunk
: All All
-- normal with 3 votes (vote)
: ---
Assigned To: general
Depends on: 249343 379818
Blocks: suiterunner
  Show dependency treegraph
Reported: 2007-04-24 12:43 PDT by Mark Banner (:standard8)
Modified: 2009-05-10 09:02 PDT (History)
12 users (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Mark Banner (:standard8) 2007-04-24 12:43:48 PDT
Profile roaming won't work in suiterunner builds due to the way it interacts with the profile (?).

We're going to leave it enabled for the time being, and if anyone wants to help with getting it to work, please do. Hopefully biesi can fill in a couple of the gaps as to what is not working.

Note that bug 377242 is a Summer of Code project which is working towards roaming profiles for Thunderbird.
Comment 1 User image Christian :Biesinger (don't email me, ping me on IRC) 2007-04-25 08:24:11 PDT
it's not working because it uses libreg to store data in the profile registry, and suiterunner doesn't use libreg for the profile list. instead it uses a plaintext file format.
Comment 2 User image Christian :Biesinger (don't email me, ping me on IRC) 2007-04-25 08:25:38 PDT
but I think this is basically the same as bug 249343
Comment 3 User image Caio Tiago Oliveira (asrail) 2007-04-25 16:01:50 PDT
I Agreed with Biese.

If you take a look at the patch or at bug 249343 comment 8 or at the marked as duplicate bug 249185, this one is strictly a duplicate.

Someone disagrees?
Comment 4 User image Caio Tiago Oliveira (asrail) 2007-04-25 16:04:10 PDT
I've changed idea (too fast).
I'll folow the TB example and just put this as depending on the other, we may require some adjustments.
Comment 5 User image Mark Banner (:standard8) 2007-05-03 01:57:22 PDT
Mailnews will soon be xpcom_obsolete free (sometime in the next week I guess), the only thing stopping building suiterunner without xpcom_obsolete is this bug.

I'd really like to stop building xpcom_obsolete in suiterunner especially given sroaming is the only part that will block us. I think we should do one of the following:

1) Don't build sroaming for suiterunner
2) ifdef & stubb out the nsIRegistry/libreg stuff (so it'll still work in xpfe - or if someone wants to turn xpcom_obsolete back on)
3) fix this bug ;-) (I don't know if looking at bug 125617 would help here).

I think given previous discussions I'd like to do option 2, as I don't see option 3 happening soon.
Comment 6 User image r.s.t 2008-10-20 08:01:56 PDT
If someone will work on roaming profiles, it would be great to solve a general problem, too:
The profile should be splitted in a small basic part (which is always local) and parts, which can be remote.
This basic part has to contain the proxy preferences, which enable the access to the remote parts. This is essential if you have to use a proxy to get internet access.
Comment 7 User image Robert Kaiser 2009-05-10 09:02:18 PDT
WONTFIX. The old sroaming will not be revived, we better should invest in getting Weave to work with SeaMonkey and replace everything we need to share between installations.

Note You need to log in before you can comment on or make changes to this bug.