From: Eric Blake <eblake@redhat.com>
To: "why do they even try?" <cygwin-talk@cygwin.com>
Subject: Re: Problems with updating nearly any package meant for Cygwin or using packages such as libtool
Date: Thu, 17 Nov 2011 21:07:00 -0000 [thread overview]
Message-ID: <4EC5778D.2080902@redhat.com> (raw)
In-Reply-To: <4EC5739F.3000600@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1214 bytes --]
On 11/17/2011 01:50 PM, Dave Korn wrote:
>> Whoops, no they can't. The hydra configure script isn't from autconf at
>> all; it's just hand-written.
>
> Good grief. It also has a Makefile.am and a Makefile.in, but it doesn't use
> automake, and their contents are unrelated. It just cats them together into
> the final makefile!
I love this quote:
https://www.gnu.org/software/autoconf/manual/autoconf.html#Pointers
> As your software is distributed to more and more users, however, you otherwise quickly find yourself putting lots of effort into reinventing the services that the GNU build tools provide, and making the same mistakes that they once made and overcame.
Autotools may not be the best out there, and might not be the easiest to
develop with, but there's hands down nothing more complete and portable
that could take over the impressive role played by the autotools in
generating predictable configure and make setups. It always makes me
cringe to see other projects that just don't get that fact, suffering
through the problems already solved by autotools.
--
Eric Blake eblake@redhat.com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 620 bytes --]
next prev parent reply other threads:[~2011-11-17 21:07 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <32849825.post@talk.nabble.com>
[not found] ` <4EC2CFA2.40007@cygwin.com>
[not found] ` <32857072.post@talk.nabble.com>
[not found] ` <4EC41689.8090601@gmail.com>
[not found] ` <32861517.post@talk.nabble.com>
[not found] ` <4EC50550.7020403@gmail.com>
[not found] ` <4EC56FB1.4000007@gmail.com>
[not found] ` <4EC570BC.2010202@gmail.com>
2011-11-17 20:51 ` Dave Korn
2011-11-17 21:07 ` Eric Blake [this message]
2011-11-17 21:32 ` Christopher Faylor
2011-11-17 22:34 ` JonY
2011-11-17 23:46 ` Charles Wilson
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=4EC5778D.2080902@redhat.com \
--to=eblake@redhat.com \
--cc=cygwin-talk@cygwin.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).