> On Fri, 8 January 2016, at 1:13 p.m., gevisz <gev...@gmail.com> wrote:
>
> 2016-01-08 13:50 GMT+02:00 Stroller <strol...@stellar.eclipse.co.uk>:
>>
>>> On Fri, 8 January 2016, at 12:32 a.m., gevisz <gev...@gmail.com> wrote:
>>>
>>> Just of curiosity compiled gtypist with nls use flag.
>>> Now it accepts ru.typ! But it is a bug because nls flag
>>> is supposed to only switch on the translation of the
>>> corresponding menu and help messages. So, it should
>>> accept ru.typ even if compiled without the nls use flag!
>>
>> I'm glad you're sorted. You should let the gtypist devs know of this bug.
>
> Thank you for your help!
>
> However, before turning to the gtypist devs, I should clarify one more,
> may be stupid, question, namely: "Who is responsible for the correct
> `functioning' of the use flags?" Because I always thought that the use
> flags are a unique feature of the Gentoo distribution (and therefore, it
> is the the Gentoo devs who are responsible for them) but your advice
> above implies that it is not true.
The ebuild is (mostly) just a wrapper for preceding software installation
tools, like make and gcc.
In a previous message you showed us that the Gtypist devs had asked you "Can
you check whether this appears when running ./configure? Also, which arguments
are used for ./configure?"
In the case of the nls USE flag, the ebuild is just calling configure with
certain arguments:
src_configure() {
econf $(use_enable nls)
}
src_install() {
emake DESTDIR="${D}" install
}
Note the IUSE variable. This lists all (non-special) use flags that are
used by the ebuild. This is used for the emerge -pv output, amongst
other things.
The package's ./configure script takes the usual --enable-nls or
--disable-nls argument. We use the use_enable utility function to
generate this automatically, depending on the user's USE flags (see
Query Functions Reference).
This is a top google hit for use_enable:
https://devmanual.gentoo.org/quickstart/
Stroller.
