As long as it isn't installing to a global location, my vote would be an opt-out for supported platforms. As it is now, the timeout config option is basically broken if a system call is what's hanging.
On Mon, Oct 5, 2009 at 1:17 PM, Chad Woolley <[email protected]>wrote: > On Mon, Oct 5, 2009 at 10:08 AM, Alexey Verkhovsky > <[email protected]> wrote: > > (1) computers behind paranoid firewalls (by adding network timeout to > every > > attempt to start an instance, which may or may not be infinite). > > (2) computers that don't have gcc or ruby-dev (increasing startup time) > > (3) you'll need to address what happens when several CC processes start > from > > the same install at the same time (because, say, I like to run builder > > processes separately from the dashboard). > > (4) possibly, computers that run CC.rb under nologin accounts. > > (5) for people who don't want the system_timer gem for any reason > > whatsoever. > > (6) ??? > > > > Seriously, a shrink-wrapped product should not silently install stuff > into > > any global library locations, IMHO. > > Good points. One note though - with Bundler, it doesn't install to a > global location, it is installed under vendor/gems. We can also do a > platform check, plus there is a 'placebo' stub gem on Windows. > > Maybe we can make the bundling automated, but only if there is an > "opt-in" flag in cruise config? Or maybe do it on all supported > platforms unless there is an "opt-out" flag set? > _______________________________________________ > Cruisecontrolrb-developers mailing list > [email protected] > http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers >
_______________________________________________ Cruisecontrolrb-developers mailing list [email protected] http://rubyforge.org/mailman/listinfo/cruisecontrolrb-developers
