From: Jeffrey Walton <noloader@gmail.com>
To: 73982@debbugs.gnu.org
Subject: bug#73982: GCC Dependency?
Date: Thu, 24 Oct 2024 03:42:01 -0400 [thread overview]
Message-ID: <CAH8yC8kmpg9FyVEV=4z9toCENLw=WbVPRtFoFA57+-LPV3aeNw@mail.gmail.com> (raw)
Hi Everyone,
I wanted to install emacs-nw, a/k/a emacs-nox, on a production Fedora
server to edit configuration files. I had to install Zile instead
because of all of Emac's dependencies, which now seems to include
compilers. Also see Red Hat Bug #2316238,
<https://bugzilla.redhat.com/show_bug.cgi?id=2316238>.
I think the dev team made a bad architectural decision when it decided
to allow the cornucopia of dependencies to grow, which now appears to
include compilers. For my use case -- a production server facing the
internet -- I do not want extra packages, like compilers and linkers.
I am not trying to help an attacker produce executable code on my
machine.
I think it would be wise to remove the requirement of a compiler for a
simple text editor. The team needs to provide a simple text editor (in
addition to the other bloated offerings).
For completeness:
$ dnf info emacs-nw
Name : emacs-nw
Epoch : 1
Version : 29.4
Release : 9.fc40
Architecture : x86_64
Size : 31 M
Source : emacs-29.4-9.fc40.src.rpm
Repository : updates
Jeff
next reply other threads:[~2024-10-24 7:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-24 7:42 Jeffrey Walton [this message]
2024-10-24 8:12 ` bug#73982: GCC Dependency? Eli Zaretskii
2024-10-24 9:15 ` Vincenzo Pupillo
2024-10-24 12:47 ` Peter Oliver
2024-10-24 13:07 ` Eli Zaretskii
2024-10-25 1:34 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-10-26 7:15 ` Eli Zaretskii
2024-10-26 20:23 ` Björn Bidar via Bug reports for GNU Emacs, the Swiss army knife of text editors
[not found] ` <87cyjmtxzm.fsf@>
2024-10-27 5:56 ` Eli Zaretskii
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='CAH8yC8kmpg9FyVEV=4z9toCENLw=WbVPRtFoFA57+-LPV3aeNw@mail.gmail.com' \
--to=noloader@gmail.com \
--cc=73982@debbugs.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).