From: fork0@t-online.de (Alex Riesen)
To: Yann Dirson <ydirson@altern.org>
Cc: Pavel Roskin <proski@gnu.org>, git <git@vger.kernel.org>
Subject: Re: Autoconf/Automake
Date: Thu, 15 Jun 2006 15:31:46 +0200 [thread overview]
Message-ID: <20060615133146.GA5794@steel.home> (raw)
In-Reply-To: <20060615072450.GF7766@nowhere.earth>
Yann Dirson, Thu, Jun 15, 2006 09:24:50 +0200:
> > Is there any interest in converting the build system used by git to
> > Autoconf and Automake? The ad-hoc configuration in Makefile is getting
> > too big. As for nice features like remembering $prefix, wouldn't it be
> > better to add them to Automake instead of limiting them to just one
> > project?
>
> Since there are many people objecting to autotools, what about using
> Jam instead ? It has the advantage of being designed to be
> cross-platform, and should have all the features we would need for *git.
Except that it is not readily available everywhere, has unreadable
and illogical syntax, and lots of unknown assumptions built in.
We are forced to use that thing at work, and it is mostly hated.
Git already has enough external dependencies (crypto, Python, Perl,
bash, gmake), why create another one?
If we are about to need a configuration system (and I doubt it), may
be we should at least select a system small enough to have it always
in git repo? (yes, as linux kernel configuration system is)
next prev parent reply other threads:[~2006-06-15 13:32 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 ` Alex Riesen [this message]
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 ` Autoconf/Automake Linus Torvalds
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=20060615133146.GA5794@steel.home \
--to=fork0@t-online.de \
--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).