Summary: | unicode profile suggestion (circumvent ncursesw issues) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Jozsef Daniel <simius> |
Component: | Eclasses | Assignee: | Gentoo Linux bug wranglers <bug-wranglers> |
Status: | VERIFIED WONTFIX | ||
Severity: | enhancement | CC: | truedfx |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Jozsef Daniel
2007-02-17 10:38:45 UTC
Sorry but creating *huge* maintenance overhead for something that's already implemented via USE=unicode is neither sane nor acceptable solution to work around a trivial issue. If you have some better solution for ncurses ebuild itself, file a bug with a patch. Separate profiles, heck no :) The whole issue is that it's NOT implemented! Have you had a look at the ncurses ebuild lately? I've filed around 2 bugs with proposed fixes already, and all of them were rejected. I'm stuck with using a custom-made ebuild in my overlay, but I'm pretty sure that there are people out there who would be happy to have unicode on their consoles out of the box. (In reply to comment #2) > The whole issue is that it's NOT implemented! Have you had a look at the > ncurses ebuild lately? What's not implemented, USE=unicode? Sorry, as said a separate profile to work around a trivial issues that requires to do `emerge --oneshot ncurses` after switching to unicode for a couple of ebuilds that don't compile otherwise is simply a no-go. (Nor is bugzilla a proper place to suggest new profiles, we have gentoo-dev mailing list for such things, though that point is pretty much moot for this particular suggestion, it won't be done). (In reply to comment #3) > (In reply to comment #2) > > The whole issue is that it's NOT implemented! Have you had a look at the > > ncurses ebuild lately? > > What's not implemented, USE=unicode? What's not implemented is a proper wide curses installation that's available to applications that rely on the standard header and standard library name. That's the whole point of bug #106820, and that's what will never be fixed, apparently. |