All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>,
	git@vger.kernel.org, "Junio C Hamano" <gitster@pobox.com>
Subject: Re: [RFC PATCH] Makefile: Turn off the configure target by default
Date: Mon, 11 Oct 2010 17:28:21 +0200	[thread overview]
Message-ID: <4CB32D15.4080204@drmicha.warpmail.net> (raw)
In-Reply-To: <201010111718.39996.jnareb@gmail.com>

Jakub Narebski venit, vidit, dixit 11.10.2010 17:18:
> Dnia poniedziałek 11. października 2010 14:10, Michael J Gruber napisał:
>> Ævar Arnfjörð Bjarmason venit, vidit, dixit 11.10.2010 11:40:
>>> On Mon, Oct 11, 2010 at 08:39, Jakub Narebski <jnareb@gmail.com> wrote:
>>>
...
>> configure is a second class citizen in git.git (we even explicitly
>> .gitignore it - if you allow that lame joke),
> 
> We .gitignore 'configure' script because it is *generated* file, and
> generated files should be not, as rule, placed under version control.

I don't know which part of "joke" was unclear?

> 
>> But, really, the typical responses to build problems with configure
>> indicate that most long timers don't use configure either, and probably
>> don't feel too comfortable with it. So, I think we should either make
>> the status quo clearer (Makefile as primary method) or change the status
>> quo. I can only do the former ;)
> 
> Because ./configure script enhances Makefile rather than generate it,
> using configure script can only improve situation (at the cost of extra
> cycles spent detecting)... well, with exception of rare cases bugs in
> configure.ac making it misdetect.

My observations on the list don't quite confirm that "configure" can
only improve the make situation, but I don't use it myself. So, I'll let
those give configure advice who use it.

Michael

  reply	other threads:[~2010-10-11 15:28 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-10-11  7:47 [RFC PATCH] Makefile: Turn off the configure target by default Michael J Gruber
2010-10-11  7:59 ` Ævar Arnfjörð Bjarmason
2010-10-11  8:39   ` Jakub Narebski
2010-10-11  9:40     ` Ævar Arnfjörð Bjarmason
2010-10-11 12:10       ` Michael J Gruber
2010-10-11 12:37         ` [RFC PATCH] Makefile: point out "make" if "make configure" fails Ævar Arnfjörð Bjarmason
2010-10-11 15:06           ` Jakub Narebski
2010-10-11 20:46             ` Sverre Rabbelier
2010-10-11 15:18         ` [RFC PATCH] Makefile: Turn off the configure target by default Jakub Narebski
2010-10-11 15:28           ` Michael J Gruber [this message]
2010-10-11 16:21             ` Ævar Arnfjörð Bjarmason
2010-10-11 16:26               ` Jonathan Nieder
2010-10-12  8:33                 ` Michael J Gruber
2010-10-12  9:10                   ` Tor Arntsen

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=4CB32D15.4080204@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=avarab@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jnareb@gmail.com \
    /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 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.