Re: Making libunistring optional

2013-01-21 Thread Andy Wingo
On Sat 17 Nov 2012 23:21, l...@gnu.org (Ludovic Courtès) writes: > Here’s an attempt to “reduce the number of dependencies” of Guile. The > approach, as suggested by Bruno Haible, uses Gnulib’s > ‘libunistring-optional’ module, along with the 22 (!) unistring modules > that provide the functional

Re: Making libunistring optional

2012-11-20 Thread Ludovic Courtès
Hi! Mark H Weaver skribis: > Yikes! It looks like this imports most of the libunistring source code > into Guile. It’s not “most of” libunistring. In terms of modules, it may be less than half of the modules that compose libunistring. But it’s definitely a big chunk of code. > If we simply

Re: Making libunistring optional

2012-11-19 Thread Noah Lavine
Hi Mark, I think you and Ludo may actually be thinking along similar lines. It seems like you're saying that you'd like one tarball that contains only Guile-specific code, and another one with Guile plus some dependencies plus maybe a nice build script. I don't have an opinion on whether to separ

Re: Making libunistring optional

2012-11-19 Thread Mark H Weaver
Hi Ludovic, l...@gnu.org (Ludovic Courtès) writes: > Here’s an attempt to “reduce the number of dependencies” of Guile. The > approach, as suggested by Bruno Haible, uses Gnulib’s > ‘libunistring-optional’ module, along with the 22 (!) unistring modules > that provide the functionality we need. >