unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Jonas Bernoulli <jonas@bernoul.li>
Cc: 58080@debbugs.gnu.org
Subject: bug#58080: 29.0.50; Don't hard-code path to pwd
Date: Mon, 26 Sep 2022 11:01:28 +0300	[thread overview]
Message-ID: <83fsgelg2v.fsf@gnu.org> (raw)
In-Reply-To: <87k05rmft6.fsf@bernoul.li> (message from Jonas Bernoulli on Sun,  25 Sep 2022 21:09:41 +0200)

> From: Jonas Bernoulli <jonas@bernoul.li>
> Date: Sun, 25 Sep 2022 21:09:41 +0200
> 
> On Guix pwd isn't located at /bin/pwd, but that path is hard-coded in
> various Makefile.in.  They deal with that by patching these files when
> building the emacs package, but when building emacs manually, that isn't
> convenient, as doing so would leave the working tree dirty, which makes
> it harder to pull whenever one of these files changes.
> 
> Please consider making this customizable so one could use, for example:
> 
>   make PWDCMD=pwd install
> 
> I assume there is a reason why the PWD variable isn't being used and
> that /bin/pwd is used because on some other OS using pwd would cause
> issues.

I don't see anything like PWDCMD in any of the GNU projects I have
here, but they do use just "pwd", not "/bin/pwd".  So maybe so should
we, and that would solve this particular problem as well?





  reply	other threads:[~2022-09-26  8:01 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 19:09 bug#58080: 29.0.50; Don't hard-code path to pwd Jonas Bernoulli
2022-09-26  8:01 ` Eli Zaretskii [this message]
2022-09-26  8:19   ` Gregory Heytings
2022-09-26  8:34     ` Andreas Schwab
2022-09-26 10:59       ` Gregory Heytings
2022-09-26 13:02         ` Gregory Heytings
2022-09-26 20:10           ` Jonas Bernoulli
2022-09-26 20:33             ` Gregory Heytings
2022-09-28 14:31               ` Gregory Heytings

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=83fsgelg2v.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=58080@debbugs.gnu.org \
    --cc=jonas@bernoul.li \
    /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).