From: Alex Vong <alexvong1995@gmail.com>
To: Mark H Weaver <mhw@netris.org>
Cc: guile-user@gnu.org, Zelphir Kaltstahl <zelphirkaltstahl@gmail.com>
Subject: Re: How to build GNUTLS Guile bindings on Xubuntu
Date: Sat, 17 Nov 2018 16:26:38 +0800 [thread overview]
Message-ID: <87muq83y9t.fsf@gmail.com> (raw)
In-Reply-To: <87tvkgxzgf.fsf@netris.org> (Mark H. Weaver's message of "Fri, 16 Nov 2018 20:30:13 -0500")
[-- Attachment #1: Type: text/plain, Size: 1564 bytes --]
Mark H Weaver <mhw@netris.org> writes:
> Hi Alex,
>
> Alex Vong <alexvong1995@gmail.com> writes:
>
>> Maybe what I wrote is not clear. What I mean is that since Debian build
>> of gnutls does not include the guile bindings, we have to build gnutls
>> from the source tarball ourselves.
>>
>> The flag "--with-guile-site-dir=/usr/local/share/guile/site/2.2"
>> instructs the build script to install the guile bindings into
>> "/usr/local/share/guile/site/2.2".
>
> Sure. This is reasonable, but for the sake of completeness, I'll point
> out two disadvantages with this approach, namely that (1) it entails
> effectively overriding Debian's GnuTLS library with your manually built
> version, which potentially affects the operation of any Debian package
> that links to GnuTLS and (2) it means staying on top of security updates
> yourself, i.e. recompiling and installing new versions of GnuTLS or the
> bundled copies of libtasn1 and libunistring when security flaws are
> discovered in those versions. Ditto for the other packages that you
> build and install manually.
>
Agree, while (1) seems to not causing problems for me in practice, (2)
is a very important point to keep in mind. Btw, this bug report[0]
explains why the guile bindings were removed. Although it's mark as
wontfix, should we encourage the maintainers to re-enable the guile
bindings in the experimental repository? The problems could perhaps be
solved by building the bindings with guile 2.2.
[0]: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=863147
> Regards,
> Mark
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2018-11-17 8:26 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-15 0:49 How to build GNUTLS Guile bindings on Xubuntu Zelphir Kaltstahl
2018-11-15 7:28 ` Mark H Weaver
2018-11-15 22:41 ` Zelphir Kaltstahl
2018-11-16 2:10 ` Mark H Weaver
2018-11-16 8:44 ` Alex Vong
2018-11-16 18:58 ` Mark H Weaver
2018-11-16 23:19 ` Alex Vong
2018-11-17 1:30 ` Mark H Weaver
2018-11-17 8:26 ` Alex Vong [this message]
2018-11-17 21:34 ` Mark H Weaver
2018-11-20 20:50 ` Ludovic Courtès
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87muq83y9t.fsf@gmail.com \
--to=alexvong1995@gmail.com \
--cc=guile-user@gnu.org \
--cc=mhw@netris.org \
--cc=zelphirkaltstahl@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).