From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 70071@debbugs.gnu.org, eliz@gnu.org, rudiwillalwaysloveyou@gmail.com
Subject: bug#70071: [FR] Provide official install scripts without requiring root, e.g., by making a static build possible
Date: Tue, 02 Apr 2024 17:41:56 -0400 [thread overview]
Message-ID: <E1rrltE-0003Um-2n@fencepost.gnu.org> (raw)
In-Reply-To: <86bk6ubvdo.fsf@gnu.org> (message from Eli Zaretskii on Sun, 31 Mar 2024 12:31:15 +0300)
[[[ To any NSA and FBI agents reading my email: please consider ]]]
[[[ whether defending the US Constitution against all enemies, ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]
> > Given that many users do not have root access, it is crucial to
> > provide an official, well-documented method for installing Emacs in
> > such environments. Addressing this issue should take precedence over
> > introducing new features, as it will significantly improve the user
> > experience and make Emacs more accessible to a wider audience.
> As already mentioned, such a method exists and is well-documented: use
> the --prefix option of the configure script to install Emacs in a
> directory to which you have access.
> This is not specific to Emacs, btw: every package that is built using
> Autoconf-produced configure script and Makefiles accepts the --prefix
> option to specify where to install it.
That feature exists in all GNU-style configure scripts, but users looking
at Emacs may not come across the text that describes it.
Maybe we should improve the Emacs documentation to specifically
mention this in a visible way.
--
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)
next prev parent reply other threads:[~2024-04-02 21:41 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-29 12:42 bug#70071: [FR] Provide official install scripts without requiring root, e.g., by making a static build possible Rudi C
2024-03-29 13:27 ` Eli Zaretskii
2024-03-29 14:24 ` Rudi C
2024-03-29 14:33 ` Eli Zaretskii
2024-03-30 1:19 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-30 12:55 ` Rudi C
2024-03-30 13:28 ` Eli Zaretskii
2024-03-30 14:31 ` Rudi C
2024-03-31 0:37 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 6:02 ` Eli Zaretskii
2024-03-31 8:39 ` Michael Albinus via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-03-31 9:06 ` Rudi C
2024-03-31 9:31 ` Eli Zaretskii
2024-04-02 21:41 ` Richard Stallman [this message]
2024-04-06 10:31 ` 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=E1rrltE-0003Um-2n@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=70071@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=rudiwillalwaysloveyou@gmail.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/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).