Re: [Abook-devel] abook portability/build-system

2014-12-05 Thread Roger
> On Fri, Dec 05, 2014 at 06:59:07PM -0300, Raphaël Droz wrote: >I recently had a look to bundled code inside abook to see how it could >be managed with a cleaner separation. Probably best to make small commits, instead of just one big patch. But I assume you already know this and were just tryin

Re: [Abook-devel] abook portability/build-system

2014-12-05 Thread Roger
Sounds good to me! Sounds like overdue atypical maintenance to me. If there's a problem, I'm sure you'll hear about it from somebody. But the risk sounds minimal versus waiting another year or so, in which something becomes deprecated and causing somebody to scramble to fix. -- Roger http:

[Abook-devel] abook portability/build-system

2014-12-05 Thread Raphaël Droz
I recently had a look to bundled code inside abook to see how it could be managed with a cleaner separation. Identified candidates were: - getopt.* - mbswidth.* - and a lot inside misc.c For example, in misc.c are defined: * varargs.h wrappers * strcasestr * vsnprintf, and thus * dopr * do