Return-Path: X-Original-To: apmail-perl-modperl-archive@www.apache.org Delivered-To: apmail-perl-modperl-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 190C0496F for ; Tue, 5 Jul 2011 09:53:58 +0000 (UTC) Received: (qmail 89464 invoked by uid 500); 5 Jul 2011 09:53:57 -0000 Delivered-To: apmail-perl-modperl-archive@perl.apache.org Received: (qmail 87625 invoked by uid 500); 5 Jul 2011 09:53:48 -0000 Mailing-List: contact modperl-help@perl.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: List-Id: Delivered-To: mailing list modperl@perl.apache.org Received: (qmail 87592 invoked by uid 99); 5 Jul 2011 09:53:41 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2011 09:53:41 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=5.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of aw@ice-sa.com designates 212.85.38.228 as permitted sender) Received: from [212.85.38.228] (HELO tor.combios.es) (212.85.38.228) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 05 Jul 2011 09:53:31 +0000 Received: from [192.168.245.129] (p549E8E45.dip0.t-ipconnect.de [84.158.142.69]) by tor.combios.es (Postfix) with ESMTPA id E0F172260C9 for ; Tue, 5 Jul 2011 11:53:09 +0200 (CEST) Message-ID: <4E12DEFC.6020309@ice-sa.com> Date: Tue, 05 Jul 2011 11:53:00 +0200 From: =?ISO-8859-1?Q?Andr=E9_Warnier?= Reply-To: mod_perl list User-Agent: Thunderbird 2.0.0.23 (Windows/20090812) MIME-Version: 1.0 To: mod_perl list Subject: Re: mod_perl EC2 AMI's or other platform providers? References: <4E118FEC.7060200@1200group.com> <4E122908.8090809@1200group.com> <9FAED9E4-43AE-4B62-AE4B-2A6F9C10D74A@gmail.com> <4E12C300.3060303@1200group.com> <7B29BA1C-3267-4EFE-90C1-625AC0635EF1@gmail.com> In-Reply-To: <7B29BA1C-3267-4EFE-90C1-625AC0635EF1@gmail.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Dave Hodgkinson wrote: > On 5 Jul 2011, at 08:53, Tosh Cooey wrote: > >> On 7/4/11 11:26 PM, Dave Hodgkinson wrote: >>>> I'm not happy, hence the complaining about the AMI from 2009. But I'm glad you changed the subject from your first one, which is that I should build my own stack. >>>> >>>> So basically you are saying (and only you, not a community voice) that in order to be a mod_perl developer one also needs to: >>>> >>>> 1) Build and optimize Apache. >>>> 2) Build and optimize MySql. >>>> 3) Build and optimize Perl+mod_perl. >>>> 4) Build and optimize a Linux server environment. >>>> or >>>> 5) Have enough money to pay for all of the above. >>> You have no stack. >>> >>> Make one. >>> >>> Better still, get a bunch of people together with the same problem. Dunno where >>> you'd find 'em. >>> >>> I just spent six months helping a company do exactly[0] this and move off a dated >>> RH platform onto a modern, current, Debian, perl 5.14, all new CPAN modules. Ah, the beauty of being able to apt-get install libapache2-mod-perl2 >> >> You seem to have missed the point of my kvetching, which is perhaps a suitable answer anyway. > > > What was the point? Rather than slinging it out in public, you may want to consider.. There are bound to be different points of view for this kind of issue, from different kinds of users. I see the same on other forums to which I subscribe (Apache, Tomcat). It is like a triangle. In corner A, there are developers who want to have the latest versions of their particular packages of interest and be able to fine-tune their setup for easy development, debugging, bug reporting etc.., but do not care very much if other packages consequently run less well on the same server. In corner B are mere users, who just want the applications to work 24/24, and could not care less about the underlying package versions as long as it does work. And in corner C are sysadmins, who are supposed to manage an ever-increasing number of servers, install something on request of A or B within the next 5 minutes, and then keep all the servers up-to-date OS-wise and many-different-packages-wise over time. Since all of them want to sleep at night and take holidays from time to time, these different positions/requirements are bound to conflict occasionally. Depending on the people involved, the size of the organisations, the budgets at stake etc, these groups may overlap or not and have different weights, so the shape and point of equilibrium of the triangle will be different in each case. And I'm sure that it's a polygon rather than a mere triangle. There certainly isn't one answer which fits all. Personally, I must say that statements like "I just spent six months helping a company do exactly[0] this" make me dream. I must be in the wrong triangle...