Return-Path: Delivered-To: apmail-apr-dev-archive@www.apache.org Received: (qmail 52963 invoked from network); 2 Jul 2004 19:33:29 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur-2.apache.org with SMTP; 2 Jul 2004 19:33:29 -0000 Received: (qmail 474 invoked by uid 500); 2 Jul 2004 19:33:37 -0000 Delivered-To: apmail-apr-dev-archive@apr.apache.org Received: (qmail 344 invoked by uid 500); 2 Jul 2004 19:33:35 -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 285 invoked by uid 99); 2 Jul 2004 19:33:33 -0000 X-ASF-Spam-Status: No, hits=0.0 required=10.0 tests=FORGED_RCVD_HELO X-Spam-Check-By: apache.org Errors-To: Message-Id: <6.1.0.6.2.20040702142002.05302ec0@pop3.rowe-clan.net> X-Sender: wrowe%rowe-clan.net@pop3.rowe-clan.net X-Mailer: QUALCOMM Windows Eudora Version 6.1.0.6 Date: Fri, 02 Jul 2004 14:21:33 -0500 To: Branko =?iso-8859-1?Q?=C4=8Cibej?= From: "William A. Rowe, Jr." Subject: Re: apr-iconv 1.0 Cc: dev@apr.apache.org In-Reply-To: <40E59F80.8020000@xbc.nu> References: <6.1.0.6.2.20040623142928.07b85ec0@pop3.rowe-clan.net> <40E4A125.2000206@xbc.nu> <6.1.0.6.2.20040702022101.0413ee38@pop3.rowe-clan.net> <40E59F80.8020000@xbc.nu> Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N At 12:46 PM 7/2/2004, Branko =C4=8Cibej wrote: >William A. Rowe, Jr. wrote: > >>At 06:41 PM 7/1/2004, Branko =C3=84=8Cibej wrote: >> >>>Thoughts? I think 1.0 is an auspicious time to make this change,= especially if we declare apr-iconv to be an implementation detail of= apr_xlate. >> >>The nifty bit is, if we declare apr-iconv to be an internal,= implementation >>detail of apr_xlate - we are free to adopt your suggestions in 1.0.1 :) >That's true. > >Then I suggest we really do close off apr-iconv. This means the apr-iconv= headers shouldn't get installed, right? Among other things. ++1 to that idea, as long as apr-util internally gets the -I / -L paths to= the build of apr-iconv, and they don't persist in the apu-1-config file. Bill