On Tue, Jan 5, 2010 at 12:00 AM, Saswata Banerjee & Associates scrapo@saswatabanerjee.com wrote:
Not exactly, This particular client had a relatively small requirement, a client servicing team that disparately needed. They are quiet happy with using windows and running the crm on it. (Rajeev gave me a list of security warnings to give them)
They had tried to use it on ubantu (as i didnt know it will run seamlessly on windows) and it failed miserably. And the project value was too small to send someone physically to the client place to install and configure ubantu and all stuff on it.
They will not look at moving to linux for crm till it becomes a product large enough or critical enough for them to invest in a new server and technical skillset to run the server
The point I was replying on was about the all-in-one installer. As JTD correctly said, it's a security problem with all-in-one installers that the end users are tied upto the version of the dependencies provided by the developers. It's not feasible for developers to release updated packages when every component will have a new release. All-in-one installers are good for quick and easy trial of the software but when you go to production you should not be using them. When moving to production, you should be using the release provided by the vendors/distibutions separately so the administrator can update each component as and when needed instead of waiting for gnukhata team to release updates that fix vulnerabilities in the other components.