unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: joakim@verona.se
To: emacs-devel@gnu.org
Subject: Alternatives for reliable build environments for emacs?
Date: Thu, 28 Oct 2021 14:55:27 +0200	[thread overview]
Message-ID: <87bl39cnr4.fsf@tanaka.verona.se> (raw)

Hello,

I'm finding it increasingly difficult to build emacs in my distro,
Fedora(Ok, I havent managed to build emacs using distro dependencies for
a long time)

What are the alternatives?

One can use for example:
- Guix
- Docker
- Flatpak

I have tried guix and docker but not yet flatpak.

These are nice because you can pin the dependency versions, to make sure
you have a reproducible build environment.

These all have the drawback that they are inconvenient when making local
modifications to the emacs source, at least for me. Way back in the days
when my original build environment worked, I automatically merged some
branches and applied local patchs with stgit, and its these kind of
things I've found awkward with the above mentioned containerized build
systems.

How are the emacs developers managing this?


Regards,

-- 
Joakim Verona
joakim@verona.se



             reply	other threads:[~2021-10-28 12:55 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-28 12:55 joakim [this message]
2021-10-28 13:33 ` Alternatives for reliable build environments for emacs? 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
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

  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=87bl39cnr4.fsf@tanaka.verona.se \
    --to=joakim@verona.se \
    --cc=emacs-devel@gnu.org \
    /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).