From new-httpd-return-1867-apmail-new-httpd-archive=apache.org@apache.org Mon Apr 03 13:16:54 2000 Return-Path: Delivered-To: apmail-new-httpd-archive@apache.org Received: (qmail 1081 invoked by uid 500); 3 Apr 2000 13:16:52 -0000 Mailing-List: contact new-httpd-help@apache.org; run by ezmlm Precedence: bulk X-No-Archive: yes Reply-To: new-httpd@apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list new-httpd@apache.org Received: (qmail 1065 invoked from network); 3 Apr 2000 13:16:52 -0000 From: pg@sweng.stortek.com Message-id: <200004031316.HAA12780@sanitas> Subject: Re: using perl in the configuration process To: new-httpd@apache.org Date: Mon, 3 Apr 2000 07:16:21 -0600 (MDT) In-Reply-To: <200004031049.GAA13361@k5.localdomain> from "Jeff Trawick" at Apr 03, 2000 06:49:31 AM X-Mailer: ELM [version 2.5 PL0] MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Spam-Rating: locus.apache.org 1.6.2 0/1000/N In a recent note, Jeff Trawick said: > Date: Mon, 3 Apr 2000 06:49:31 -0400 > > > Which platforms Apache support doesn't have Perl as standard these days? > > OS/390, AIX, Windows, OS/2, AS/400, ... (if what you mean by > "standard" is that it comes with the system and thus it won't be a > burden for anyone) > I believe that Perl is more readily available and more current for OS/390 than autoconf/m4/etc. Autoconf is OK if it runs at the provider end and the consumer need only run the generated shell scripts. -- gil -- StorageTek INFORMATION made POWERFUL