Full specification gets remarkably unmanageable when you decide to
change something. Having tried it both ways the design decision I took
was to stick to specifying the major software items as lightly as
possible and let the machines deal with pulling in the rest. Otherwise
your list of modules is four foot long and you end up being unable to
see the wood for the trees.<br>
<br>
My goal is automation with flexibility. What gets in the way is tools
that assume there is a human sat at a terminal or, worse, clicking with
a mouse. gem is at fault here, not mongrel but nobody seems to be
fixing gem at the moment - the patches to fix the platform problem are
already in the gem tracker.<br><br><div><span class="gmail_quote">On 04/06/06, <b class="gmail_sendername">James Moore</b> <<a href="mailto:banshee@banshee.com" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
banshee@banshee.com</a>> wrote:</span><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
> Tried that - local gem install doesn't handle dependencies automatically<br><br>Is that much of an issue for deployment, though? Seems like you want to<br>know precisely what's installed on production servers, and having
<br>dependencies resolved for you isn't quite so much of an issue.<br><br> - James Moore<br><br>_______________________________________________<br>Mongrel-users mailing list<br><a href="mailto:Mongrel-users@rubyforge.org" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
Mongrel-users@rubyforge.org</a><br><a href="http://rubyforge.org/mailman/listinfo/mongrel-users" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">http://rubyforge.org/mailman/listinfo/mongrel-users</a>
<br></blockquote></div><br><br clear="all"><br>-- <br>Neil Wilson (<a href="mailto:neil@aldur.co.uk" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)">
neil@aldur.co.uk</a>)