Greetings, I have been trying to figure out what the best way to work with ONNV when making changes.
Right now, I have a workspace directory with the tarballs for b72 extracted within. My process looks like this: 1) change / add the files relevant to what I'm doing 2) copy the changed / added files to my mercurial checkout of the ONNV gate 3) generate a diff using "hg diff" from the root 4) post a text file describing the change, testing, etc. along with the relevant .patch file (containing the diffs) 5) dump my temporary workspace copy 6) re-extract the source drop 7) revert my mercurial checkout of the ONNV gate This seems rather tedious to do for every change. What do you folks do when making changes to ONNV? Do you work / build nightlies out of your mercurial directory? Do you commit them to a local mercurial repository? If so, can you tell me what setup you have? I haven't found the "sweet spot" yet to make this process easier. When I was originally making contributions, the mercurial gate wasn't even up yet, so I just worked with an original extracted copy of the source tree and a working copy of the source tree from tarballs. Suggestions are welcomed, -- Shawn Walker, Software and Systems Analyst [EMAIL PROTECTED] - http://binarycrusader.blogspot.com/ "Beware of bugs in the above code; I have only proved it correct, not tried it. " --Donald Knuth _______________________________________________ opensolaris-code mailing list opensolaris-code@opensolaris.org http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
