all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: c.buhtz@posteo.jp
To: 62484@debbugs.gnu.org
Subject: bug#62484: Join INSTALL and INSTALL.REPO
Date: Mon, 27 Mar 2023 13:40:20 +0000	[thread overview]
Message-ID: <f72ab77552755e939f4a95bcf89d9f5c@posteo.de> (raw)

Hello,

IMHO it is unusual that a build system depends on if I use a tarball or 
a git repo. Never seen this before. No matter that there might be good 
technical reason to this it should be adopted to the "usual" users.

A user does look into a README first, finds no build infos and then 
looks for a BUILD file. Can't find one and tries INSTALL (which is not 
intended to have build infos because build and install are different 
things). User (me) found an INSTALL and stuck to it. 
configure-make-system is usual and known. No need to read all the docs 
from the beginning (where the link is to the exception INSTALL.REPO). So 
I just started at "2." and it failed because I used a git repo instead 
of a tarball.

You see.

IMHO it would improve the things if you would join INSTALL and 
INSTALL.REPO back together and also put a TOC on top of it.

I assume there is technically no way to remove the difference between 
tarball-build and git-build, right?

Kind
Christian

Related to:
62482@debbugs.gnu.org
62480@debbugs.gnu.org





             reply	other threads:[~2023-03-27 13:40 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-27 13:40 c.buhtz [this message]
2023-03-27 15:45 ` bug#62484: Acknowledgement (Join INSTALL and INSTALL.REPO) GNU bug Tracking System
2023-03-30  6:18   ` Jean Louis
2023-09-06  0:01 ` bug#62484: Join INSTALL and INSTALL.REPO Stefan Kangas
2023-09-06  0:02 ` bug#62484 acknowledged by developer (Re: bug#62484: Join INSTALL and INSTALL.REPO) GNU bug Tracking System

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=f72ab77552755e939f4a95bcf89d9f5c@posteo.de \
    --to=c.buhtz@posteo.jp \
    --cc=62484@debbugs.gnu.org \
    --cc=bug-gnu-emacs@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 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.