From: Michael Welsh Duggan <mwd@md5i.com>
To: peder@news.klingenberg.no (Peder O. Klingenberg)
Cc: emacs-devel@gnu.org
Subject: Re: proposal: require GnuTLS 3.1.x (previous stable)
Date: Wed, 26 Nov 2014 08:46:45 -0500 [thread overview]
Message-ID: <87y4qyula2.fsf@maru2.md5i.com> (raw)
In-Reply-To: <ks4mtm8gt7.fsf@netfonds.no> (Peder O. Klingenberg's message of "Wed, 26 Nov 2014 10:14:12 +0100")
peder@news.klingenberg.no (Peder O. Klingenberg) writes:
> On Tue, Nov 25 2014 at 18:55, Ivan Shmakov wrote:
>
>> Yes, although I’d rather question the necessity of building
>> Emacs ‘master’ on an LTS GNU/Linux system. If the intent is to
>> use the last decade’s versions of Libc and Coreutils, – why
>> Emacs has to be newer than that?
>
> Because features. My desktop machine runs Kubuntu 10.04 still, because
> it mostly does what I need without needing my attention all the time, it
> is a stable platform I can use to get work done.
>
> There is no conscious desire to run old software for nostalgias sake,
> more a lack of desire to upgrade willy-nilly with the associated
> breakage-fixing and retraining of muscle memory because some dimwits
> decided to reinvent everything badly.
Moreover, not everyone has complete control over their desktop. At work
we have RHEL6. I build Emacs for my own use. I could build gnutls as
well, but my (recent) experience of that is hellish. gnutls requires
nettle and gmp. I build nettle, and then find out that gnutls doesn't
support the latest nettle. So I grab an older nettle and build that.
Then it complains about HOGWEED. Oh, libgmp needs to be installed
_before_ nettle is built to get HOGWEED. I wish that had been
mentioned. At this point, I give up for the day because I have to get
real work done.
--
Michael Welsh Duggan
(md5i@md5i.com)
prev parent reply other threads:[~2014-11-26 13:46 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 18:38 Build failure (master; MS-Windows) Dani Moncayo
2014-11-23 21:41 ` Dani Moncayo
2014-11-23 22:07 ` Lars Magne Ingebrigtsen
2014-11-23 22:52 ` Dani Moncayo
2014-11-23 22:57 ` Lars Magne Ingebrigtsen
2014-11-23 23:09 ` Dani Moncayo
2014-11-25 9:32 ` proposal: require GnuTLS 3.1.x (previous stable) (was: Build failure (master; MS-Windows)) Ted Zlatanov
2014-11-25 15:57 ` proposal: require GnuTLS 3.1.x (previous stable) Lars Magne Ingebrigtsen
2014-11-25 16:28 ` Ted Zlatanov
2014-11-25 16:38 ` Buildbot for Emacs? (was: proposal: require GnuTLS 3.1.x (previous stable)) Lars Magne Ingebrigtsen
2014-11-25 16:50 ` Buildbot for Emacs? Glenn Morris
2014-11-25 16:55 ` Ted Zlatanov
2014-11-25 22:15 ` Glenn Morris
2014-11-25 23:12 ` Ted Zlatanov
2014-11-26 9:52 ` Tom
2014-11-25 17:05 ` Lars Magne Ingebrigtsen
2014-11-25 22:14 ` Glenn Morris
2014-11-25 17:34 ` proposal: require GnuTLS 3.1.x (previous stable) Stefan Monnier
2014-11-25 18:55 ` Ivan Shmakov
2014-11-26 9:14 ` Peder O. Klingenberg
2014-11-26 12:57 ` Ivan Shmakov
2014-11-26 13:47 ` Peder O. Klingenberg
2014-11-26 13:08 ` Ted Zlatanov
2014-11-26 14:12 ` Peder O. Klingenberg
2014-11-26 15:42 ` Stefan Monnier
2014-11-26 16:52 ` Ted Zlatanov
2014-11-26 21:18 ` Ted Zlatanov
2014-11-26 21:37 ` Lars Magne Ingebrigtsen
2014-11-27 2:13 ` Stefan Monnier
2014-11-27 2:33 ` Ted Zlatanov
2014-11-28 18:51 ` Ted Zlatanov
2014-11-28 19:31 ` Stefan Monnier
2014-11-29 20:02 ` Glenn Morris
2014-11-26 13:46 ` Michael Welsh Duggan [this message]
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/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87y4qyula2.fsf@maru2.md5i.com \
--to=mwd@md5i.com \
--cc=emacs-devel@gnu.org \
--cc=peder@news.klingenberg.no \
/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/emacs.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).