Dave, My build is not headless, but it takes some time and I would like to be able to start it and come back later to find it done. With my newest image, the pre-flight checklist drove me nuts, but it avoided three things (in succession, it might help to collect a nag list in one shot) that would have stopped the build after wasting varying amounts of time. However, my clean test might not have been fair, because looking back, I'm not sure I disabled the warnings for that pass. My message is that opening the help on initialization adds little value while increasing complexity of the setup and/or adding risk of bringing the process to a halt. IMHO, the line should be removed. I am loading command shell only to get the pipes; someone planning to use the shell might see this differently. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of David T. Lewis Sent: Wednesday, November 25, 2009 4:25 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] OSProcess load On Tue, Nov 24, 2009 at 11:18:45PM -0500, Schwab,Wilhelm K wrote:
Dave,
I did get .40. However, it seems to be much better behaved if the help is not displayed. AFAICT, removing the line avoids the interruption of what should be an unattended process.
My build process now disables the deprecation warnings.
Bill, Just so I understand, is this a problem because the extra window opening is an annoyance, or because the deprecation warnings (for #isMorphic) cause a problem, or is it because you are doing the builds with a headless image and this actually interrupts the process? I just want to make sure I fix the right problem, not just a workaround. Thanks, Dave _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project