This is the mail archive of the
mailing list for the Cygwin project.
Re: gettext packaging bug?
- From: Charles Wilson <cygwin at cwilson dot fastmail dot fm>
- To: cygwin-apps at cygwin dot com
- Date: Thu, 13 Jun 2013 15:01:43 -0400
- Subject: Re: gettext packaging bug?
- References: <20130612151316 dot GG30807 at calimero dot vinschen dot de> <51B8C746 dot 4000203 at cwilson dot fastmail dot fm> <51B93371 dot 8020206 at users dot sourceforge dot net>
On 6/12/2013 10:50 PM, Yaakov (Cygwin/X) wrote:
On 2013-06-12 14:08, Charles Wilson wrote:
However, in actuality, neither Bruno's "gettext-runtime" (our gettext)
nor his "gettext-tools" (our gettext-devel) really represent a
"traditional" runtime-vs-devel split.
Note that this means all of the following:
are actually in 'gettext' and *not* in gettext-devel.
IMO they really should be in the latter; if you're building a package
which uses l10n, you need it anyway for autopoint, msgfmt, etc.
Right, which is why gettext-devel *should* (and on 32bit, does) depend
However, I'll investigate how the linux distros package gettext & co.
It's possible TRTD is to have libintl-devel, libasprintf-devel,
libgettextpo-devel, etc...and (most of) gettext-devel is transferred to
gettext-tools. As I said, I'll investigate.