From: David Woodhouse <dwmw2@infradead.org>
To: Eric Anopolsky <erpo41@gmail.com>
Cc: Christian Parpart <trapni@gentoo.org>, linux-btrfs@vger.kernel.org
Subject: Re: [PATCH] btrfs-progs: autotoolized and splitup into {libbtrfs,tools,tests}
Date: Thu, 09 Oct 2008 23:07:23 +0100 [thread overview]
Message-ID: <1223590043.28324.83.camel@macbook.infradead.org> (raw)
In-Reply-To: <1223589129.7861.61.camel@telesto>
On Thu, 2008-10-09 at 15:52 -0600, Eric Anopolsky wrote:
> On Thu, 2008-10-09 at 15:55 +0200, Christian Parpart wrote:
> > On Thursday 09 October 2008 12:45:06 David Woodhouse wrote:
> > > On Thu, 2008-10-09 at 04:20 +0200, Christian Parpart wrote:
> > > > this now makes use of autoconf/automake/libtool suite,
> > >
> > > Please, God, no.
> > >
> > > I will personally buy a licence for GNU make for anyone who needs one.
> >
> > In that case, you shall know what license automake is under, too,
> > and despite your impressions i read above, if you don't want it, fine with me,
> > but stick to reasonable facts instead of religios talk next time you press a
> > reply button.
>
> I nearly tried to make an argument against the autotools last night.
> Today, I decided that I would rather explain why I had such a visceral
> reaction to the announcement and not try to convince anyone of anything.
>
> The GNU autotools kept me out of FOSS development for the better part of
> a decade.
>
> They obviously solve a common and important problem, or they wouldn't be
> so widespread.
Really, do they? In my experience, they cause more problems than they
solve. It's mostly just cargo-cult programming.
If you have decent, portable code, and decent makefiles, you really
don't need the baroque pile of turd that autotools inflicts on you.
If I ever see a btrfs-progs build trying to detect what kind of FORTRAN
compiler I have on the system, I'm never going to touch btrfs-progs
again. Life's just too bloody short to deal with that kind of crap.
--
dwmw2
next prev parent reply other threads:[~2008-10-09 22:07 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-09 2:20 [PATCH] btrfs-progs: autotoolized and splitup into {libbtrfs,tools,tests} Christian Parpart
2008-10-09 5:55 ` Christoph Hellwig
2008-10-09 6:47 ` Christian Parpart
2008-10-09 10:45 ` David Woodhouse
2008-10-09 13:55 ` Christian Parpart
2008-10-09 21:52 ` Eric Anopolsky
2008-10-09 22:07 ` David Woodhouse [this message]
2008-10-10 1:01 ` Christian Parpart
2008-10-10 6:38 ` David Woodhouse
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=1223590043.28324.83.camel@macbook.infradead.org \
--to=dwmw2@infradead.org \
--cc=erpo41@gmail.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=trapni@gentoo.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