bug#62484: Join INSTALL and INSTALL.REPO

bug#62484: Join INSTALL and INSTALL.REPO

[c.buhtz]

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

bug#62484: Acknowledgement (Join INSTALL and INSTALL.REPO)

[GNU bug Tracking System]

Thank you for filing a new bug report with debbugs.gnu.org.

This is an automatically generated reply to let you know your message
has been received.

Your message is being forwarded to the package maintainers and other
interested parties for their attention; they will reply in due course.

Your message has been sent to the package maintainer(s):
 bug-gnu-emacs@gnu.org

If you wish to submit further information on this problem, please
send it to 62484@debbugs.gnu.org.

Please do not send mail to help-debbugs@gnu.org unless you wish
to report a problem with the Bug-tracking system.

-- 
62484: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62484
GNU Bug Tracking System
Contact help-debbugs@gnu.org with problems

bug#62484: Acknowledgement (Join INSTALL and INSTALL.REPO)

[Jean Louis]

* GNU bug Tracking System <help-debbugs@gnu.org> [2023-03-27 19:06]:
> Thank you for filing a new bug report with debbugs.gnu.org.

> If you wish to submit further information on this problem, please
> send it to 62484@debbugs.gnu.org.

I have not filed this report, but I have got confirmation.

--
Jean

Take action in Free Software Foundation campaigns:
https://www.fsf.org/campaigns

In support of Richard M. Stallman
https://stallmansupport.org/

bug#62484: Join INSTALL and INSTALL.REPO

[Stefan Kangas]

tags 62484 wontfix notabug
close 62484
thanks

c.buhtz@posteo.jp writes:

> 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.

Unfortunately, I think that would just confuse the situation even more.
Users building from the tarball should not have to worry about the
details in INSTALL.REPO.  This takes priority over users pulling the git
repository.

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

Correct.

On balance, I'm closing this bug.  Sorry.

bug#62484 acknowledged by developer (Re: bug#62484: Join INSTALL and INSTALL.REPO)

[GNU bug Tracking System]

This is an automatic notification regarding your bug report
#62484: Join INSTALL and INSTALL.REPO,
which was filed against the emacs package.

Thank you for your report, which has now been closed.
You can view the full report at
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62484

If you require further information, please followup to 62484@debbugs.gnu.org.

debbugs.gnu.org maintainers
(administrator, GNU bugs database)