Hi Gábor,
On Thu, 2 Apr 2020, SZEDER Gábor wrote:
> On Sun, Mar 29, 2020 at 05:12:31PM +0700, Đoàn Trần Công Danh wrote:
> > Signed-off-by: Đoàn Trần Công Danh <congdanhqx@xxxxxxxxx>
>
> > + set -ex
> > + cd /usr/src/git
> > + test -n "$cache_dir" && ln -s "$cache_dir/.prove" t/.prove
> > + autoconf
> > + echo "PYTHON_PATH=/usr/bin/python3" >config.mak
> > + ./configure --with-libpcre
>
> The recommended way to build Git is without autoconf and configure.
That is news to me.
My understanding still is that `make` is the recommended way to build Git,
and `./configure` is only for those who want to use autoconf.
It seems that the `INSTALL` file agrees with my understanding:
-- snip --
Git installation
Normally you can just do "make" followed by "make install", and that
will install the git programs in your own ~/bin/ directory. If you want
to do a global install, you can do
$ make prefix=/usr all doc info ;# as yourself
# make prefix=/usr install install-doc install-html install-info
# ;# as root
(or prefix=/usr/local, of course). Just like any program suite
that uses $prefix, the built results have some paths encoded,
which are derived from $prefix, so "make all; make prefix=/usr
install" would not work.
The beginning of the Makefile documents many variables that affect the way
git is built. You can override them either from the command line, or in a
config.mak file.
Alternatively you can use autoconf generated ./configure script to
set up install paths (via config.mak.autogen), so you can write instead
$ make configure ;# as yourself
$ ./configure --prefix=/usr ;# as yourself
$ make all doc ;# as yourself
# make install install-doc install-html;# as root
-- snap --
If you think that I am wrong, I invite you to change the recommendation by
proposing a patch to `INSTALL`, to change the current recommendation.
Ciao,
Dscho
