From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1760900AbXGEOv7 (ORCPT ); Thu, 5 Jul 2007 10:51:59 -0400 Received: (majordomo@vger.kernel.org) by vger.kernel.org id S1760280AbXGEOvs (ORCPT ); Thu, 5 Jul 2007 10:51:48 -0400 Received: from moutng.kundenserver.de ([212.227.126.174]:51183 "EHLO moutng.kundenserver.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1757570AbXGEOvr (ORCPT ); Thu, 5 Jul 2007 10:51:47 -0400 From: Bodo Eggert <7eggert@gmx.de> Subject: Re: [ANNOUNCE] util-linux-ng 2.13-rc1 To: Nix , Karel Zak , List util-linux-ng , linux-kernel@vger.kernel.org, linux-fsdevel@vger.kernel.org Reply-To: 7eggert@gmx.de Date: Thu, 05 Jul 2007 16:50:54 +0200 References: <8CYT9-4Ou-23@gated-at.bofh.it> <8Dh9k-8lT-3@gated-at.bofh.it> <8DtDz-3xC-15@gated-at.bofh.it> User-Agent: KNode/0.7.2 MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: 8Bit Message-Id: X-be10.7eggert.dyndns.org-MailScanner-Information: See www.mailscanner.info for information X-be10.7eggert.dyndns.org-MailScanner: Found to be clean X-be10.7eggert.dyndns.org-MailScanner-From: 7eggert@gmx.de X-Provags-ID: V01U2FsdGVkX1//Wj4+sPBmBbMTsTLL4zQ5K7tdy4LhcrM+Yo1 Uu3EvQG8X8g3s3n0fPrP6g9f9vdCRCH7qdT8KlheFKg7hDi9Cw HBYr1lfo1AmLSqASBO0Pg== Sender: linux-kernel-owner@vger.kernel.org X-Mailing-List: linux-kernel@vger.kernel.org Nix wrote: > On 4 Jul 2007, DervishD stated: >> Anyway, if you don't like mobs or you just don't want to try it, >> that's fine, but please don't use autotools, it doesn't make much sense >> for a linux only project, since you will be using only the "directory >> choosing" part of autotools. Maybe a hand made script will help (and I > > Oh, yeah, great, another hand-rolled build system. That's *juwt* what > those of us who have autotools working well (with config.site's that > do all we need and then some) are looking forward to. > > There are advantages to standardization, you know. A *lot* of > autobuilders know how to make autoconf-generated configure scripts jump > through hoops. I was downright *happy* when util-linux was > autoconfiscated: I could ditch the code to handle automatic > configuration of yet another one-package hand-rolled build system. Standardisation is good, but autotools (as they are used) usurally isn't. It tests for the availability of a fortran compiler for a C-only project, checks the width of integers on i386 for projects not caring about that and fails to find installed libraries without telling how it was supposed to find them or how to make it find that library. Configuring the build of an autotools program is harder than nescensary; if it used a config file, you could easily save it somewhere while adding comments on how and why you did *that* choice, and you could possibly use a set of default configs which you'd just include. The Makefiles generated by autotools is a huge mess, if autotools got it wrong (again!), fixing them requires editing a lot of files. I'm really really happy if I read 'edit Makefile.conf and run make...'. -- No matter which way you have to march, its always uphill. Friß, Spammer: n@kqYYs.7eggert.dyndns.org mlygzw.k@d.7eggert.dyndns.org cDmOEZ@z-luqs.7eggert.dyndns.org .-@IfuiUgj.7eggert.dyndns.org