mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Nix <nix@esperi.org.uk>
To: List util-linux-ng <util-linux-ng@vger.kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org
Subject: Re: [ANNOUNCE] util-linux-ng 2.13-rc1
Date: Fri, 06 Jul 2007 07:42:02 +0100	[thread overview]
Message-ID: <87zm2aav9h.fsf@hades.wkstn.nix> (raw)
In-Reply-To: <20070705205523.GA15202@suse.de> (Bernhard Walle's message of "Thu, 5 Jul 2007 22:55:24 +0200")

On 5 Jul 2007, Bernhard Walle stated:

> * Nix <nix@esperi.org.uk> [2007-07-05 22:42]:
>> 
>> My only real grouch with cmake is that the authors have invented a
>> language with so bloody many capital letters in it. 
>
> The real problem I see with cmake is that you need to have cmake
> installed on the build system.

I don't see that as being very much more of a problem than having make
installed (except of course that make is defined by POSIX and cmake is
not). The real problem is that nearly all the cmake macros are shipped
with cmake itself, so version-dependent scripts are more common, and
instead of being hit with `you need at least this version of GNU make,
released in 1998' you're likely to get hit with `you need at least this
version of cmake, released three months ago' which is more likely to
annoy the poor users.

>                                While cmake itself isn't the problem,
> often, it also depends on the version of cmake that is installed. The
> good idea about auto* tools is the idea that you don't need to install
> any tools to build, just to develop. A POSIX shell and Perl should be
> installed everywhere ...

You don't need Perl to run configure scripts, either, and it's only
recently that it started requiring a POSIX shell rather than something
of the calibre of Solaris's /bin/sh.



(But I'm spamming this list so I'll shut up now.)

  reply	other threads:[~2007-07-06  6:42 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [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 19:20       ` DervishD
2007-07-05 20:42         ` Nix
2007-07-05 20:55           ` Bernhard Walle
2007-07-06  6:42             ` Nix [this message]
2007-07-06  7:19               ` Mike Frysinger
2007-07-06 22:43                 ` Nix
2007-07-06  6:41           ` DervishD
2007-07-06  7:17             ` Mike Frysinger
2007-07-06 10:43               ` DervishD
2007-07-06 12:17         ` Bodo Eggert
2007-07-06 12:51           ` DervishD
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-06  0:30         ` Bryan Henderson
2007-07-06  1:16           ` Mike Frysinger
2007-07-06 16:50             ` Bryan Henderson
2007-07-03 22:11 Karel Zak
2007-07-04  8:42 ` Christoph Hellwig
2007-07-04 10:34   ` David Miller
2007-07-05 16:41   ` Mike Frysinger
2007-07-05 18:04     ` Andreas Dilger
2007-07-05 21:30     ` Karel Zak
2007-07-06  0:38       ` Matthew Wilcox
2007-07-05 23:03   ` Jeff Garzik
2007-07-06  9:01     ` Gerd Hoffmann
2007-07-06  9:16       ` Jeff Garzik
2007-07-06 19:35       ` Joel Becker
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

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=87zm2aav9h.fsf@hades.wkstn.nix \
    --to=nix@esperi.org.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox

all inboxes | Powered by JetHome®