Hi,
Daniel Hartwig skribis:
> By the way, I very much like the conventions used in the GnuTLS
> bindings. The enums in particular make a lot of sense for a security
> library, with the extreme type safety they provide. I will pursue a
> similar approach.
Yeah, I think it’s helpful.
> One que
On Sat 09 Feb 2013 16:12, l...@gnu.org (Ludovic Courtès) writes:
> An issue with the FFI is distros where .la and .so files are only
> available in the -dev package, because then ‘dynamic-link’ won’t work
> unless that -dev package is installed (as recently discussed on
> guile-user.)
I have the
Hi Andy,
Andy Wingo writes:
> On Sat 09 Feb 2013 16:12, l...@gnu.org (Ludovic Courtès) writes:
>
>> An issue with the FFI is distros where .la and .so files are only
>> available in the -dev package, because then ‘dynamic-link’ won’t work
>> unless that -dev package is installed (as recently dis
Mark,
I agree with everything you said about dependencies. I think the real
solution is something like what you said - sharing code, but bundling.
One way to push that farther would be to distribute tarballs that include
the complete source of some libraries, and somehow making a combined build
s
Mark H Weaver skribis:
> Andy Wingo writes:
>
>> On Sat 09 Feb 2013 16:12, l...@gnu.org (Ludovic Courtès) writes:
>>
>>> An issue with the FFI is distros where .la and .so files are only
>>> available in the -dev package, because then ‘dynamic-link’ won’t work
>>> unless that -dev package is ins
On 6 February 2013 21:13, Nala Ginrut wrote:
> /usr/share/mime is contained in 'shared-mime-info' package, at least for
> openSUSE. The suggestion you gave means Guile will depend on this
> package. Personally, I don't think that's what you want. ;-P
Hi
The suggestion was to support reading the
