From: Jeff Garzik <jeff@garzik.org>
To: Christoph Hellwig <hch@infradead.org>,
Karel Zak <kzak@redhat.com>,
List util-linux-ng <util-linux-ng@vger.kernel.org>,
linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng 2.13-rc1
Date: Thu, 05 Jul 2007 19:03:26 -0400 [thread overview]
Message-ID: <468D78BE.4030902@garzik.org> (raw)
In-Reply-To: <20070704084211.GA19128@infradead.org>
Christoph Hellwig wrote:
> On Wed, Jul 04, 2007 at 12:11:56AM +0200, Karel Zak wrote:
>> The package build system is now based on autotools. The build system
>> supports separate CFLAGS and LDFLAGS for suid programs (SUID_CFLAGS,
>> SUID_LDFLAGS). For more details see the README file
>
> And this is really dumb. autotools is a completely pain in the ass and
> not useful at all for linux-only tools.
A myth. It is quite useful for packagers, because of the high Just
Works(tm) factor. After porting an entire across several revisions of a
distro, the autotools-based packages are the ones that work out of the
box 90% of the time.
The other 90% of _my_ time comes from annoying people who roll their own
Makefile/build solution, which the packager has to then learn.
It's just not scalable for people to keep building their own build
solutions.
Jeff
next prev parent reply other threads:[~2007-07-05 23:03 UTC|newest]
Thread overview: 56+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-03 22:11 [ANNOUNCE] util-linux-ng 2.13-rc1 Karel Zak
2007-07-03 22:11 ` Karel Zak
2007-07-04 8:42 ` Christoph Hellwig
2007-07-04 8:42 ` Christoph Hellwig
2007-07-04 10:34 ` David Miller
2007-07-04 10:34 ` David Miller
2007-07-05 16:41 ` Mike Frysinger
2007-07-05 16:41 ` Mike Frysinger
2007-07-05 18:04 ` Andreas Dilger
2007-07-05 21:30 ` Karel Zak
2007-07-05 21:30 ` Karel Zak
2007-07-06 0:38 ` Matthew Wilcox
2007-07-05 23:03 ` Jeff Garzik [this message]
2007-07-06 9:01 ` Gerd Hoffmann
2007-07-06 9:16 ` Jeff Garzik
2007-07-06 19:35 ` Joel Becker
2007-07-06 19:35 ` Joel Becker
2007-07-09 7:20 ` Gerd Hoffmann
2007-07-09 7:20 ` Gerd Hoffmann
2007-07-09 20:18 ` Mike Frysinger
2007-07-04 11:11 ` Jan Engelhardt
2007-07-05 17:22 ` H. Peter Anvin
2007-07-04 17:47 ` DervishD
2007-07-05 7:01 ` Nix
[not found] <8CYT9-4Ou-23@gated-at.bofh.it>
[not found] ` <8Dh9k-8lT-3@gated-at.bofh.it>
[not found] ` <8DtDz-3xC-15@gated-at.bofh.it>
2007-07-05 14:50 ` Bodo Eggert
2007-07-05 14:50 ` Bodo Eggert
2007-07-05 19:20 ` DervishD
2007-07-05 19:20 ` DervishD
2007-07-05 20:42 ` Nix
2007-07-05 20:42 ` Nix
2007-07-05 20:55 ` Bernhard Walle
2007-07-05 20:55 ` Bernhard Walle
2007-07-06 6:42 ` Nix
2007-07-06 7:19 ` Mike Frysinger
2007-07-06 7:19 ` Mike Frysinger
2007-07-06 22:43 ` Nix
2007-07-06 22:43 ` Nix
2007-07-06 6:41 ` DervishD
2007-07-06 6:41 ` DervishD
2007-07-06 7:17 ` Mike Frysinger
2007-07-06 10:43 ` DervishD
2007-07-06 10:43 ` DervishD
2007-07-06 12:17 ` Bodo Eggert
2007-07-06 12:17 ` Bodo Eggert
2007-07-06 12:51 ` DervishD
2007-07-06 12:51 ` DervishD
2007-07-05 20:36 ` Nix
2007-07-05 20:36 ` Nix
2007-07-05 21:30 ` Mike Frysinger
2007-07-05 21:34 ` Nix
2007-07-05 21:47 ` Mike Frysinger
2007-07-05 21:47 ` Mike Frysinger
2007-07-06 0:30 ` Bryan Henderson
2007-07-06 0:30 ` Bryan Henderson
2007-07-06 1:16 ` Mike Frysinger
2007-07-06 16:50 ` Bryan Henderson
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=468D78BE.4030902@garzik.org \
--to=jeff@garzik.org \
--cc=hch@infradead.org \
--cc=kzak@redhat.com \
--cc=linux-fsdevel@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=util-linux-ng@vger.kernel.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 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.