Stephen Lau wrote:
Okay, so we have the list of tools we need to port at:
http://opensolaris.org/sc/src/scm-migration/docs/devtools.html
(it's updated from the SCM repository)
So now comes the fun part, who wants to work on what?
IIRC, Darren Moffat volunteered to do webrev. I know Rich Lowe has done
*some* work on wx, whether that translates into him volunteering for
it... well, we'll see. I'll just publicly call him out here and see
what his response is ;-)
I can't exactly test the more important bits of wx, so that kinda
complicates things.
Since you mentioned webrev, that has dependencies on workflow choices.
The way it needs to work differs pretty significantly depending on
whether Mq is used.
(of course, the same is also true of wx)
Anyone else?
We've got the scm-migration/ongk repository which currently houses the
gatekeeper tools. The developer tools (with the exception of
zbringover, which I don't think should be priority 1) are within ON
under usr/src/tools/scripts. How do people want to do this? Should I
just create a clone of onnv-gate into a Mercurial repository
(scm-migration/devtools), and we can work within that? It seems a
little overkill to import all of ON for that... and given that we're
whacking in entirely new support, I don't know how useful it will be for
us to need to have the history around. I'm fine creating a new repo and
dumping in fresh copies of just the tools we need, in the interest of
bandwidth and space. Let me know what you guys think.
Will the tools build standalone? If so, just the tools. If not, no. :)
_______________________________________________
tools-discuss mailing list
tools-discuss@opensolaris.org
