unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Bhavin Gandhi <bhavin7392@gmail.com>
To: 52488@debbugs.gnu.org
Subject: bug#52488: Try basename of agrv0's realpath for .pdmp lookup in libexecdir
Date: Wed, 15 Dec 2021 00:55:25 +0530	[thread overview]
Message-ID: <CAOn=hbejWYEBE-YPZa5uman1Ja5=jLAAi1XYPkL5sw9VOFim+Q@mail.gmail.com> (raw)
In-Reply-To: <CAOn=hbcpRgtyq3j3oxDZo5Y0+akNUBfHdyX8O+=ECPBp7U0wbw@mail.gmail.com>

On Wed, 15 Dec 2021 at 00:32, Bhavin Gandhi <bhavin7392@gmail.com> wrote:
>
> Why do you want that?
>
> As the comment from load_pdump_find_executable explains, there are
> setups where the /usr/bin/emacs is a symlink managed by something like
> alternatives. This symlink eventually points to an Emacs binary like
> emacs-28.0.90. These kind of setups are used to have installation of
> multiple versions of Emacs on the same system.
>
> Supporting resolution of these symlinks while searching for a .pdmp file
> will make it possible to put the .pdmp files in libexecdir instead of
> putting those in the /usr/bin/. I think this should be in addition to
> the possibilities tried currently.

Consider a scenario where /usr/bin/emacs-nox is a symlink to
emacs-28.0.90-nox. And we have emacs-nox.pdmp in libexecdir. This will
work with current implementation. But if Emacs is invoked directly as
emacs-28.0.90-nox, then it will fail.


> > Why don't you configure each Emacs build with a different libexecdir
> > instead?
>
> Sure, but there are some common files in that directory like hexl,
> movemail, etc, which package maintainers have put into a common package
> like emacs-common.

This part of the message has nothing to do with the current bug report,
it is creating confusion.





  reply	other threads:[~2021-12-14 19:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14 19:01 bug#52488: Try basename of agrv0's realpath for .pdmp lookup in libexecdir Bhavin Gandhi
2021-12-14 19:25 ` Bhavin Gandhi [this message]
2021-12-14 19:32 ` Ken Brown
2021-12-15 17:56   ` Ken Brown
2021-12-15 18:19     ` Glenn Morris
2021-12-15 18:53       ` Ken Brown
2021-12-15 22:08         ` Ken Brown
2021-12-19 12:57           ` Lars Ingebrigtsen
2021-12-19 15:26             ` Ken Brown
2021-12-23 13:48               ` Ken Brown
2021-12-23 13:50               ` Bhavin Gandhi
2021-12-15 18:24     ` Bhavin Gandhi
2021-12-15 19:32       ` Eli Zaretskii
2021-12-14 19:42 ` 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='CAOn=hbejWYEBE-YPZa5uman1Ja5=jLAAi1XYPkL5sw9VOFim+Q@mail.gmail.com' \
    --to=bhavin7392@gmail.com \
    --cc=52488@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).