Re: Source code, git and cvs

[uzibalqa]

------- Original Message -------
On Friday, July 21st, 2023 at 4:35 AM, Eli Zaretskii <eliz@gnu.org> wrote:


> > Date: Thu, 20 Jul 2023 15:47:32 +0000
> > From: uzibalqa uzibalqa@proton.me
> > Cc: help-gnu-emacs@gnu.org
> > 
> > ------- Original Message -------
> > On Friday, July 21st, 2023 at 3:36 AM, Eli Zaretskii eliz@gnu.org wrote:
> > 
> > > > Can this detail be included in README ? Because currently README only
> > > > describes INSTALL.
> > > 
> > > INSTALL itself already includes that information:
> > > 
> > > For information about building from a Git checkout (rather than an
> > > Emacs release), read the INSTALL.REPO file first.
> > 
> > I do not like the idea that information is stored deeper and deeper
> > in hierarchy. They are two separate things and should be mentioned
> > in the README. Not having to read about where to find information
> > about installing from the repo using the file intended to show how
> > to install from the tarball.
> > 
> > Do not make it difficult for users to get to the basic information
> > they need.
> 
> 
> I think it makes it easier, because INSTALL is a definitely a file
> people who want to install will read, whereas README is a more
> general-purpose file which doesn't necessarily need to say anything
> about installation.
> 
> > README should describe both immediately at the start. Not just about
> > installing from the tarball.
> 
> 
> We clearly disagree.

Of course, hide it and make things more difficult for new users.   And then 
expect them to figure out things by themselves.   And when they ask questions,
never be straightforward and give them the code they need to use.  It is their
job to go through the ever increasing obfuscation of information embedded within
deeper and deeper levels of cyclomatic complexity.  Classic example of 
development 
malpractice.

  
smart approach.