SeaMonkey/1.9.1 Repository Options
There are (at least) three ways to organize the SeaMonkey repository for 1.9.1:
Option A: The best but hardest way
In this option, the seamonkey repository is the "parent" of the mozilla-central repository, and pulls it using something like client.py.
suite/ mailnews/ configure.in (*not* the mozilla configure.in: a separate one just for seamonkey) config/config.mk config/rules.mk Makefile.in check out mozilla-central into mozilla/ using some client.py-like solution mozilla/configure.in mozilla/xpcom/... mozilla/toolkit/...
The suite repository has an independent configure script which calls into the mozilla configure script.
Option B: flattening the suite into a single directory
The next option is to stick all the suite files into a single directory, and check out that directory into the mozilla-central tree somehow:
xpcom/... configure.in suite/mailnews suite/components suite/...
This makes compiling the suite pretty much the same as now, except for some directories that have moved. You can clone http://hg.mozilla.org/seamonkey-central to suite/ in a meta-checkout script.
Option B2: have a separate repo for each major component that's logically separate, e.g.
suite-central (most suite-specific stuff, checked out to suite/...) chatzilla (checked out to extensions/irc) thunderbird-central (checked out to mail/ or mailnews/ or something)