all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Rudi C <rudiwillalwaysloveyou@gmail.com>
Cc: luangruo@yahoo.com, 70071@debbugs.gnu.org
Subject: bug#70071: [FR] Provide official install scripts without requiring root, e.g., by making a static build possible
Date: Sun, 31 Mar 2024 09:02:27 +0300	[thread overview]
Message-ID: <86sf07aqh8.fsf@gnu.org> (raw)
In-Reply-To: <CAE9z9A1CSiyFw7_jgsngWZgYg3Ut=WC6bVRmk_kbZ+4FNEzgqw@mail.gmail.com> (message from Rudi C on Sat, 30 Mar 2024 18:01:31 +0330)

> From: Rudi C <rudiwillalwaysloveyou@gmail.com>
> Date: Sat, 30 Mar 2024 18:01:31 +0330
> Cc: luangruo@yahoo.com, 70071@debbugs.gnu.org
> 
> Given my lack of root access, I'm unsure about the best approach to install these libraries. Manually writing an
> installer script for every missing Emacs dependency raises concerns, as these dependencies might have
> their own dependencies, making the task complex, error-prone, and time-consuming. This approach may not
> be the most practical or efficient solution for the majority of users, and it certainly isn't the simple two-liner
> that your previous messages suggested. The complexity involved in manually resolving dependencies is
> precisely the reason I turned to package managers like Linuxbrew, Guix, and Nix in the first place.

If those libraries are for some reason not installed on the system,
and if the sysadmins cannot be asked to install them, then you will
need to build and install them yourself, yes.  What it takes is to
configure each one of them with --prefix= pointing to some directory
under your home directory, and then using the LIBS variable at
configure time to tell the Emacs build procedure to search those
directories for libraries.  IOW, this is the same "simple two-liner"
we showed in previous messages, just repeated for every library you
needto install privately.  And if the libraries aren't and cannot be
installed system-widely, what else can be done about that?

Of course, if package managers allow you to install precompiled
binaries and their prerequisites in any directory you like, by all
means use them.  The Emacs project doesn't (and cannot) maintain those
package managers, but they exist for these purposes, so using them
when they solve your problems is indeed TRT.





  parent reply	other threads:[~2024-03-31  6:02 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=86sf07aqh8.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=70071@debbugs.gnu.org \
    --cc=luangruo@yahoo.com \
    --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 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.