X-Recipient: archive-cygwin AT delorie DOT com
X-SWARE-Spam-Status: No, hits=-1.8 required=5.0 	tests=AWL,BAYES_00,J_CHICKENPOX_72,J_CHICKENPOX_92,RCVD_IN_DNSWL_LOW,SPF_PASS,TRACKER_ID
X-Spam-Check-By: sourceware.org
Message-ID: <49D4221F.5040100@cwilson.fastmail.fm>
Date: Wed, 01 Apr 2009 22:25:35 -0400
From: Charles Wilson <cygwin AT cwilson DOT fastmail DOT fm>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.8.1.21) Gecko/20090302 Thunderbird/2.0.0.21 Mnenhy/0.7.6.666
MIME-Version: 1.0
To: cygwin AT cygwin DOT com
Subject: Re: [ANNOUNCEMENT] [1.5] Updated: {gettext/gettext-devel/libgettextpo0/libintl8/libasprintf0}-0.17-3
References: <announce DOT 495E4607 DOT 9090309 AT cwilson DOT fastmail DOT fm> <4987C6D1 DOT 5080200 AT users DOT sourceforge DOT net> <49D19FD0 DOT 2020501 AT users DOT sourceforge DOT net>
In-Reply-To: <49D19FD0.2020501@users.sourceforge.net>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
Sender: cygwin-owner AT cygwin DOT com
Mail-Followup-To: cygwin AT cygwin DOT com
Delivered-To: mailing list cygwin AT cygwin DOT com

Yaakov (Cygwin/X) wrote:
>> I've been testing this patch[1] for some time within Ports, and it has
>> solved a lot of the problems I was having with libtool-2.2.  Could you
>> please consider this for inclusion in your gettext package?
> 
>> [1] http://cygwin.com/ml/cygwin/2008-10/msg00346.html

Well, I'm not too thrilled about automatically upgrading every package
that uses gettext to the latest version -- even those that aren't being
built *for cygwin* itself.  Basically, with your patch, if you do an
autoreconf on the cygwin platform, then you're going to bump to
gettext-0.17 no matter what you've listed in your configure.ac.

That's fine -- probably -- for cygport'ed packages being built *for*
cygwin.  Not so fine for packages that are merely being developed ON
cygwin as the development host (I've been told that there are folks who
do that).

However, there is a /real/ bug in older gettexts that you've encountered
and are trying to work around.  And, it's best if that workaround were
somewhat automated (e.g. otherwise you'd just say "edit configure.ac and
change the value of AM_GNU_GETTEXT_VERSION").

What we need is an "out of band" method of communicating to autopoint --
even when it is invoked indirectly by autoreconf -- that you do, or do
not, want to respect the value of AM_GNU_GETTEXT_VERSION in configure.ac.

Seems to me the right way to do that is an environment variable. If
autopoint was sensitive to, say:

AUTOPOINT_FORCE_GETTEXT_VERSION

then you could ensure that cygport (always?) sets that variable to
(e.g.) 0.17 (or maybe a magic value "CURRENT_INSTALLED" or something).

Does that seem like a reasonable approach to you?

--
Chuck

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/