git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Yann Dirson <ydirson@altern.org>
Cc: Alex Riesen <raa.lkml@gmail.com>, Pavel Roskin <proski@gnu.org>,
	git <git@vger.kernel.org>
Subject: Re: Autoconf/Automake
Date: Thu, 15 Jun 2006 15:54:34 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0606151545050.5498@g5.osdl.org> (raw)
In-Reply-To: <20060615211454.GK7766@nowhere.earth>



On Thu, 15 Jun 2006, Yann Dirson wrote:
> 
> In tha case of jam, the doc issue can certainly be raised, but the
> most prominent problem is probably that everyone and their dog knows
> make,

Oh, I agree. A "simpler" thing that people don't know is often much 
inferior to a complex thing that people are generally intimately familiar 
with.

I just personally believe that autoconf/automake are the worst of both 
worlds (ie it's a _complex_ thing that a lot of people don't know).

GNU make in many ways is actually not that bad. Yeah, the makefiles get 
more complex, but it's usually not totally unreadable, and you can do some 
clever stuff with it. 

The kernel makefiles are a pretty extreme example (and it hides a lot of 
the complexity in files that get included and that most people never ever 
need to look at). I suspect that git could more easily do something like 
that (on a _much_ smaller scale - don't get me wrong).

			Linus

  reply	other threads:[~2006-06-15 22:54 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-06-14 22:27 Autoconf/Automake Pavel Roskin
2006-06-14 22:45 ` Autoconf/Automake Linus Torvalds
2006-06-14 22:54 ` Autoconf/Automake Bertrand Jacquin
2006-06-14 23:18 ` Autoconf/Automake Timo Hirvonen
2006-06-15  7:24 ` Autoconf/Automake Yann Dirson
2006-06-15 13:31   ` Autoconf/Automake Alex Riesen
2006-06-15 16:32     ` Autoconf/Automake Yann Dirson
2006-06-15 17:02       ` Autoconf/Automake Linus Torvalds
2006-06-15 17:48         ` Autoconf/Automake Olivier Galibert
2006-06-15 18:03           ` Autoconf/Automake Jakub Narebski
2006-06-15 18:19             ` Autoconf/Automake Olivier Galibert
2006-06-16 18:23             ` Autoconf/Automake Petr Baudis
2006-06-16  9:06           ` Autoconf/Automake Jerome Lovy
2006-06-15 20:17         ` Autoconf/Automake Yakov Lerner
2006-06-15 21:14         ` Autoconf/Automake Yann Dirson
2006-06-15 22:54           ` Linus Torvalds [this message]
2006-06-15 23:10             ` Autoconf/Automake Johannes Schindelin
2006-06-16  6:51               ` Autoconf/Automake Nikolai Weibull
2006-06-15 20:10     ` Autoconf/Automake Phil Richards
2006-06-15 20:32       ` Autoconf/Automake Timo Hirvonen
2006-06-15 20:42       ` Autoconf/Automake Johannes Schindelin
2006-06-15 22:05         ` Autoconf/Automake Yann Dirson
2006-06-15 22:58           ` Autoconf/Automake Johannes Schindelin
2006-06-16 20:17             ` Autoconf/Automake Yann Dirson
2006-06-16 20:42               ` Autoconf/Automake Petr Baudis
2006-06-16 18:31           ` Autoconf/Automake Petr Baudis

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=Pine.LNX.4.64.0606151545050.5498@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=proski@gnu.org \
    --cc=raa.lkml@gmail.com \
    --cc=ydirson@altern.org \
    /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).