You are not logged in.
I've already typed this out in the message I sent to BTG's mailing list, but here's the short of it:
I just adopted the AUR package for BTG, a 3-part torrent client. When I enable the ncurses interface in the configure flags, I get an error about having wide-character support in ncurses. According to the BTG devs, their application won't work with wide-character support, and they suggest that Arch is doing it wrong.
The question is, I don't really think that we should have split packages for ncurses. Of course, that's a decision for the devs, but it doesn't seem like the kind of thing they'd accept, so I didn't bother posting a bug report for it.
Do I just accept that one of the three interfaces to BTG won't work in Arch, and keep the other parts maintained and working? Also, I just noticed that someone posted a patch to the configure script that would allow successful compilation, but I'm not sure what that would do to the stability of the app. Should I apply the patch in the pkgbuild and just test it really, really thoroughly?
Last edited by Xiong Chiamiov (2009-01-21 08:11:07)
Offline
The app should compile just fine using the wide character libraries - the wide and non-wide versions are API compatible. I have no idea what they are actually doing that would cause a problem with the wide character version... Give the patch a try.
Offline
Alrighty, I went ahead and put the patch in the pkgbuild, and it seems to work well enough. I'll be using the ncurses part of the app fairly often, so I should be able to notice any strange behavior. Thanks for the advice.
Offline