You didn't mention in your post the "alternative" view - only that you believe its great but with no counter argument to the points I raised. Can you be more specific where I am getting it wrong so that I can learn. I'm coming to ruby, rails and aaf(ferret) with a brand new set of eyes, I am a noobie in every sense and if I see it wrong then I want to be told as such. The capistrano issues I raised for example were for the most part resolveable and now all they need to do is needed is capture that in the official documentation.
I comment on it not to rubbish but to begin the process of fixing the behaviour in a cluster and production behaviour. Should my comments and solutions be acceptable I am willing to put my coding time where my mouth is and implement the solutions, because I NEED it for my app to be able to work properly. Its not like any of the other solutions are good either. Gem V plugin is always going to rage, I simply can't get the plugin to work with a svn:// url so I don't have the option to use it, which means I can't run aaf at all because I have to have a basic cluster because rails requires it! As I said in my post if the gem is going to be published it should come with the necessary tools to get a Drb server started, it seems like a simple enough change (I hope) and one that will allow me to reenable my ferret support in my app. As for rejection as spam I don't know what is going wrong there, I don't even have the spam filter turned on, are you doing the maths question? -- Posted via http://www.ruby-forum.com/. _______________________________________________ Ferret-talk mailing list [email protected] http://rubyforge.org/mailman/listinfo/ferret-talk
