From: Jakub Narebski <jnareb@gmail.com>
To: Han-Wen Nienhuys <hanwen@xs4all.nl>
Cc: git@vger.kernel.org
Subject: Re: bug: git-sh-setup should not be in $PATH
Date: Wed, 6 Dec 2006 17:27:53 +0100 [thread overview]
Message-ID: <200612061727.54058.jnareb@gmail.com> (raw)
In-Reply-To: <4576E9DF.5090709@xs4all.nl>
Dnia środa 6. grudnia 2006 17:03, Han-Wen Nienhuys napisał:
> Jakub Narebski escreveu:
>
>> The fact that I didn't understood what this part of patch is meant
>> to do should be the big hint that this commit needs some longer commit
>> message explaining purpose of such mess.
>>
>> I still don't understand what this part do (and how come it is
>> in configure.ac which should be _only_ about generating
>> config.mak.autogen Makefile configuration file and _not_ about
>> generating Makefiles). You want what sequence of commands to work?
>>
>> $ $srcdir/configure --srcdir=$srcdir
>> $ make -D $srcdir
>> $ make -D $srcdir DESTDIR=$DESTDIR install
>
> make -D doesn't exist.
Oops. I meant make -C, not make -D.
> This is about
>
> mkdir git-build
> cd git-build
> $my_git_source/configure
> make
>
> this _was_ actually documented in that one-line commit message, that
> you found to be too short.
Because it was so short (one line) while being long for one line.
Why don't you write above in commit message?
> Since git does recursive makes, among others in
>
> perl/
> Documentation/
> templates/
> contrib/
>
> there should be Makefiles in said directories. Otherwise, every rule
> in the toplevel Makefile saying
>
>
> $(MAKE) -C subdir/
>
> will fail because $builddir/ does not have a Makefile in
> $builddir/subdir.
Wouldn't it be better just to modify toplevel Makefile to say:
$(MAKE) -C $(srcdir)/subdir/
without messing with ./configure script, and creating "redirect"
Makefiles?
> The part you don't understand is a generic way of duplicating the
> Makefiles from the git sources, while making sure that they work when
> $srcdir != $builddir
>
>
> Yes, if builddir != srcdir , then configure is about more than
> generating config.mak.autogen
Once again: git is not autotool'ed project. Everything you want to
do should work regardless if you would run ./configure, or if you
would hand-craft config.mak file.
--
Jakub Narebski
next prev parent reply other threads:[~2006-12-06 16:25 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-06 12:14 bug: git-sh-setup should not be in $PATH Han-Wen Nienhuys
2006-12-06 12:23 ` Johannes Schindelin
2006-12-06 12:34 ` Han-Wen Nienhuys
2006-12-06 12:56 ` Jakub Narebski
2006-12-06 14:16 ` Han-Wen Nienhuys
2006-12-06 14:51 ` Jakub Narebski
2006-12-06 15:03 ` Han-Wen Nienhuys
2006-12-06 15:27 ` Jakub Narebski
2006-12-06 15:36 ` Han-Wen Nienhuys
2006-12-06 15:56 ` Jakub Narebski
2006-12-06 16:03 ` Han-Wen Nienhuys
2006-12-06 16:27 ` Jakub Narebski [this message]
2006-12-06 16:40 ` Han-Wen Nienhuys
2006-12-06 16:52 ` Jakub Narebski
2006-12-06 16:56 ` Han-Wen Nienhuys
2006-12-06 17:11 ` Jakub Narebski
2006-12-07 13:36 ` Andreas Ericsson
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=200612061727.54058.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@xs4all.nl \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).