From: Kei Kebreau <kei@openmailbox.org>
To: ng0 <ngillmann@runbox.com>
Cc: guix-devel@gnu.org
Subject: Re: [PATCH] gnu: lynx: Fix GnuTLS support.
Date: Sat, 08 Oct 2016 12:22:27 -0400 [thread overview]
Message-ID: <87twcm7qv0.fsf@openmailbox.org> (raw)
In-Reply-To: <87r37rnds6.fsf@we.make.ritual.n0.is> (ng0's message of "Sat, 08 Oct 2016 13:58:17 +0000")
[-- Attachment #1: Type: text/plain, Size: 784 bytes --]
ng0 <ngillmann@runbox.com> writes:
> Hi,
>
> Kei I think you need to consider packaging one of the "pre" versions of
> lynx. I understand we are fixed on packaging this with gnutls, so if you
> read the changelog of the recent pre versions releases, you will
> discover that there was work on gnutls support. If you don't want to
> package pre version itself, there might be patches directly. I don't
> know how this all works together and it wasn't my intention to find out
> when I looked into this, but we should really consider to package recent
> pre release of lynx. Note that this is not dev, dev is more experimental
> than pre.
>
I only see lynx 2.8.9 development tarballs. I don't have a problem
targeting those temporarily if it is acceptable to package it and it works.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 818 bytes --]
next prev parent reply other threads:[~2016-10-08 16:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-10-07 0:48 [PATCH] gnu: lynx: Fix GnuTLS support Kei Kebreau
2016-10-07 1:28 ` Leo Famulari
2016-10-07 1:56 ` Tobias Geerinckx-Rice
2016-10-07 2:02 ` Tobias Geerinckx-Rice
2016-10-07 6:27 ` ng0
2016-10-07 14:42 ` Kei Kebreau
2016-10-08 13:58 ` ng0
2016-10-08 16:22 ` Kei Kebreau [this message]
2016-10-08 21:47 ` Leo Famulari
2016-10-09 17:55 ` Kei Kebreau
2016-10-09 19:20 ` Leo Famulari
2016-10-09 20:16 ` Kei Kebreau
2016-10-09 20:36 ` Leo Famulari
2016-10-09 21:00 ` Kei Kebreau
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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87twcm7qv0.fsf@openmailbox.org \
--to=kei@openmailbox.org \
--cc=guix-devel@gnu.org \
--cc=ngillmann@runbox.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).