The newest ratpoison (1.4.4; the ebuild needs bumping), should use the following USE flags: xft readline At the moment they're just found automagically. The debian builds do this already, see http://git.savannah.gnu.org/cgit/ratpoison.git/tree/debian/rules for details. Reproducible: Always Steps to Reproduce:
Created attachment 189959 [details, diff] Patch that moves the ebuild to EAPI=2 and adds IUSE=history I cannot find anything in the ratpoison sources related to x11-libs/libXft, so I ignored that - it could well be that Debian uses that integrally and then ignores the configure warnings for packages that simply don't support xft... Anyway, this patch introduces IUSE=history, which has the build system use or not use readline's libhistory. If that satisfies your needs, I will commit it shortly.
This patch (IUSE=+history) entered into the fresh 1.4.4 ebuild (version bump).
That patch looks good, and thanks for bumping, but it looks to me in the new (1.4.4) release that there are libXft options in the configure script, which affect the code. This is new in this release, I believe. It would be worth adding this flag then, too, to control whether --without-xft is passed to ./configure, as this is the kind of option the super-minimalists who are likely to be attracted to ratpoison may like. Thanks
Well spotted! In revision 1.4.4-r1, IUSE=xft has been added (as well as debug support).
That's great, and working well for me. Thanks alot!
