Re: [ANNOUNCEMENT] [1.5] Updated: {gettext/gettext-devel/libgettextpo0/libintl8/libasprintf0}-0.17-3

["Yaakov (Cygwin/X)" <yselkowitz at users dot sourceforge dot net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Charles Wilson wrote:
> 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.

Yes, it essentially changes the meaning of the AC_GNU_GETTEXT_VERSION
argument from == to >=.

> 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).

Hmmm, hadn't thought about that, although I don't understand why an
actively developed package shouldn't be using gettext-0.17 already.

> 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").

Exactly.

> 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?

What about enabling the autopoint -V option (which is currently
commented out as "dangerous" on lines 164-166,212-222), and changing the
version mismatch error on line 276 into a message or warning?  Cygport
could then export AUTOPOINT="autopoint -V 0.17" when libtool usage is
detected.


Yaakov
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEAREIAAYFAknUKO0ACgkQpiWmPGlmQSN4ZQCeNOC6nxiJrZHcUSdhYacfOWFR
4G4AnjBxD0HpN7RZy9xIvw0LzSwlV8su
=Ng29
-----END PGP SIGNATURE-----

--
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/