[gnutls-dev] Integrating Guile bindings?

[Simon Josefsson]

ludovic.courtes at laas.fr (Ludovic Courtès) writes:

> Simon Josefsson <simon at josefsson.org> writes:
>
>> I have GnuTLS installed in /usr/lib (from Debian) and newer libraries in
>> /usr/local/lib.  Configuring guile-gnutls results in:
>
> [...]
>
>> Linking an application with those parameters won't make it use
>> libgnutls.so from /usr/local/lib, a -Wl,-rpath or similar is required
>> too.
>>
>> This results in 'make check' failing.
>>
>> Modifying LD_LIBRARY_PATH is ugly.  It is a bad recommendation.
>>
>> I believe configure should simply work automatically in this not at all
>> uncommon situation.
>
> Yeah, I usually use a similar setting (home-built lib in `/usr/local')
> and work around this by having `LD_LIBRARY_PATH' include
> `/usr/local/lib'.  There's nothing wrong with updating
> `LD_LIBRARY_PATH', though, as it is required anyway to get the right lib
> loaded.

The problem with LD_LIBRARY_PATH is that every user on the system that
wants to use an application linked without library search paths will
have to modify LD_LIBRARY_PATH.  Not everyone build application just for
their own use, and those who do, requiring users to set LD_LIBRARY_PATH
is problematic.

>> Oh, yes, right, one requirement to add anything to the core GnuTLS
>> package is that the copyright is transferred to the FSF
>
> I guess that would fall under my copyright assignment for GnuTLS, so I'd
> basically just need to change the copyright line in each file and we're
> done.

Yup.  There is nobody else who contributed code, or where you copied
code written by someone else?

>> and that
>> generally it follows the GNU project's standards (which, among other
>> things, imply that the manual is GFDL).  You should read:
>>
>> http://www.gnu.org/prep/standards/
>> http://www.gnu.org/prep/maintain/
>
> This should be ok.  If you notice any specific point where it deviates
> from the standards, please let me know.

When/if we integrate it, I'll review it further.

/Simon