From: worik <root@worik.org>
To: "H. Dieter Wilhelm" <dieter@duenenhof-wilhelm.de>
Cc: 53627@debbugs.gnu.org
Subject: bug#53627: 29.0.50; Incorrect installation instructions
Date: Sun, 30 Jan 2022 10:52:13 +1300 [thread overview]
Message-ID: <9dc96b58-e2e1-89c1-1b09-364b4ae2df66@worik.org> (raw)
In-Reply-To: <xm46zgnetdq8.fsf@duenenhof-wilhelm.de>
On 30/01/22 10:48, H. Dieter Wilhelm wrote:
> worik <root@worik.org> writes:
>
>> * Downloaded: git clone https://github.com/Stazed/rakarrack-plus.git
> Please read INSTALL.REPO in the same directory, it says
I can cope. I did not need that file. I was not asking for help. I
was reporting a bug.
Having incorrect installation instructions in a file labeld INSTALL and
repeating them in a file named README is a bug.
It is not much help to have the correct instructions in some other file.
cheers
Worik
>
> Building and Installing Emacs from the Repository
>
> ...
> To use the autotools, run the following shell command to generate the
> 'configure' script and some related files, and to set up your git
> configuration:
>
> $ ./autogen.sh
>
> You can then configure your build as follows:
>
> $ ./configure
>
>
>> * Read INSTALL
>>
>> * Tells me to run `./configure`
>>
>> * That does not exist. README references it too
>>
>> * Must run `./autogen.sh` first
--
If not me then who? If not now then when? If not here then where?
So, here I stand, I can do no other
root@worik.org 021-1680650, (03) 4821804 Aotearoa (New Zealand)
next prev parent reply other threads:[~2022-01-29 21:52 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 21:39 bug#53627: 29.0.50; Incorrect installation instructions worik
2022-01-29 21:48 ` H. Dieter Wilhelm
2022-01-29 21:52 ` worik [this message]
2022-01-29 22:05 ` H. Dieter Wilhelm
2022-01-30 6:27 ` Eli Zaretskii
2022-01-30 1:50 ` Po Lu via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-01-30 22:54 ` Benjamin Riefenstahl
2022-01-31 15:25 ` Lars Ingebrigtsen
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=9dc96b58-e2e1-89c1-1b09-364b4ae2df66@worik.org \
--to=root@worik.org \
--cc=53627@debbugs.gnu.org \
--cc=dieter@duenenhof-wilhelm.de \
/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.