From: Robert Pluim <rpluim@gmail.com>
To: joakim@verona.se
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: Alternatives for reliable build environments for emacs?
Date: Thu, 28 Oct 2021 17:29:50 +0200 [thread overview]
Message-ID: <87cznpw4k1.fsf@gmail.com> (raw)
In-Reply-To: <87v91hb2dc.fsf@tanaka.verona.se> (joakim@verona.se's message of "Thu, 28 Oct 2021 17:22:39 +0200")
>>>>> On Thu, 28 Oct 2021 17:22:39 +0200, joakim@verona.se said:
>> Thatʼs the first Iʼve heard of it. GnuTLS too old, too new, something else?
joakim> Too new in Fedora(at the time before I threw in the towel at least).
OK. Iʼll guess we'll start seeing reports at some point then.
>> Debian has always worked ok for me. Although I donʼt target
>> reproducible builds.
joakim> Well, I could likely build emacs just fine in a docker container using
joakim> debian as the base, and run the container in my host fedora os. I know
joakim> some people do this. This approach is also brittle with how to manage
joakim> the src tree for development.
I just point my dockers at a local directory, then you donʼt need to worry
about volume persistence.
Robert
--
next prev parent reply other threads:[~2021-10-28 15:29 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-28 12:55 Alternatives for reliable build environments for emacs? joakim
2021-10-28 13:33 ` Eli Zaretskii
2021-10-28 14:38 ` joakim
2021-10-28 14:45 ` Robert Pluim
2021-10-28 15:22 ` joakim
2021-10-28 15:29 ` Robert Pluim [this message]
2021-10-28 19:09 ` Tassilo Horn
2021-10-29 6:14 ` Po Lu
2021-10-28 16:08 ` Eli Zaretskii
2021-10-28 17:37 ` joakim
2021-10-28 20:37 ` Pierre Téchoueyres
2021-10-29 0:29 ` Yuchen Pei
2021-10-29 6:14 ` Eli Zaretskii
2021-11-03 6:53 ` Yuchen Pei
2021-10-28 16:07 ` Yuri Khan
2021-10-28 20:20 ` Daniel Martín
2021-10-28 19:02 ` Stefan Monnier
2021-10-28 19:58 ` Tim Cross
2021-10-28 21:35 ` joakim
2021-10-30 6:52 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87cznpw4k1.fsf@gmail.com \
--to=rpluim@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=joakim@verona.se \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.