On Fri, Apr 20, 2007 at 12:50:50PM -0700, Garrett D'Amore wrote:
> I might have a go at updating nightly. Do you have anything written out
> in more detail about this problem? I'm imaging the problem is that it
> needs to know about /usr/closed vs. /usr/src, right?
>
Yeah, at the moment we've already got nightly ported to understand hg.
We punted on having it understand the split repository model for Hg
until we determine what the best way to deal with them being in two
separate repositories. Basically, if you look at the repositories, we
have 2 Hg repos:
onnv-gate (which contains usr/)
closed (which contains everything under closed, e.g.: uts/, cmd/, etc.)
so if you do a 'hg clone onnv-gate myonnv' you'll get:
myonnv/
|---usr/
|--src/
and to get a full tree, you'd then do a:
(cd myonnv/usr; hg clone onnv-gate-closed)
which would create closed/ under usr/
(make sense?)
So basically nightly needs to be taught to understand both repositories
such that if the nightly does a bringover/pull, it should only pull the
usr/src repo if closed/ isn't present; but if both usr/src and
usr/closed are present, then pull both. The trickier thing is what to
do if no repositories have been checked out yet (i.e.: you're doing a
nightly with only a .env file and no pre-existing source). I think in
this case we want to pull just the open tree.
I think that sums it up in a nutshell.
BTW, we have a project alias: scm-migration-dev at opensolaris.org
Let me know if you want me to add you to the mailing list. Please send
any code review, etc. to the list for people to look at.
cheers,
steve
--
stephen lau // stevel at sun.com | 650.786.0845 | http://whacked.net
opensolaris // solaris kernel development
