On 05/12/16 06:13 AM, konsolebox wrote:
> Hi,
>
> Please consider promoting the use of tinfo flag in packages that
> depend on sys-libs/ncurses so that they would synchronize properly
> with sys-libs/ncurses[tinfo].
>
> It could be as simple as:
>
> IUSE="tinfo"
>
> RDEPEND="sys-libs/ncurses[tinfo=]"
>
> pkg_setup() {
> use tinfo && export LDFLAGS="-ltinfo ${LDFLAGS}" LIBS="-ltinfo ${LIBS}"
> }
>
> The last line can be changed/enhanced, depending on the package.
>
> It helps keep binaries consistent even if sys-libs/ncurses[-tinfo]
> gets recompiled to sys-libs/ncurses[tinfo], because they are forced to
> be recompiled. This is better than hard-coded dynamic workarounds.
> Should this message perhaps have been directed to a particular set of developers or package maintainers rather than everyone on this list? I'm not sure what our stance is on propagating USE flags to rdeps when the package itself doesn't care (except due to the --libs output changing from pkg-config). I feel that adding tinfo to IUSE the way it's suggested here might be the only technical solution right now, but at the same time it seems like something that might be better suited to something that should be addressed through other mechanisms in a future-EAPI... Note in particular though that the pkg_setup example ISN'T imo a good idea -- rather, pkg-config should be used, as it will return the appropriate --libs output whether ncurses is built with USE=tinfo enabled or not.
signature.asc
Description: OpenPGP digital signature
