From dev-return-11213-apmail-apr-dev-archive=apr.apache.org@apr.apache.org Thu Mar 04 23:03:00 2004 Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 56574 invoked from network); 4 Mar 2004 23:03:00 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 4 Mar 2004 23:03:00 -0000 Received: (qmail 79783 invoked by uid 500); 4 Mar 2004 23:02:46 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 79621 invoked by uid 500); 4 Mar 2004 23:02:45 -0000 Mailing-List: contact dev-help@apr.apache.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: Delivered-To: mailing list dev@apr.apache.org Received: (qmail 79608 invoked from network); 4 Mar 2004 23:02:45 -0000 Date: Thu, 04 Mar 2004 15:02:57 -0800 From: Justin Erenkrantz To: Aaron Bannert , dev@apr.apache.org Subject: Re: apr/apr-util python dependence Message-ID: <2147483647.1078412577@st-augustin.ics.uci.edu> In-Reply-To: <20040304185803.GA565@clove.org> References: <40364711.5040708@algroup.co.uk> <2147483647.1077275770@dhcp31-55.ics.uci.edu> <20040304185803.GA565@clove.org> X-Mailer: Mulberry/3.1.2 (Mac OS X) MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline X-Spam-Level: X-Spam-Status: No, hits=0.0 required=5.0 tests=none autolearn=unavailable version=2.70-r6256 X-Spam-Checker-Version: SpamAssassin 2.70-r6256 (2004-01-23) on scotch.ics.uci.edu X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N --On Thursday, March 4, 2004 10:58 AM -0800 Aaron Bannert wrote: > On Fri, Feb 20, 2004 at 11:16:10AM -0800, Justin Erenkrantz wrote: >> It'd be trivial to have minotaur run ./buildconf before producing the >> snapshots. This would lower the barrier of entry on the snapshots: >> you'd no longer need autoconf, libtool, etc to use those. -- justin > > Isn't libtool still needed for the build process? I don't see how running > ./buildconf would eliminate the libtool dependency. Uh, no. When you run buildconf, libtool copies all of its files into the tree. It's self-contained at that point. -- justin