From: Stephen Hemminger <shemminger@vyatta.com>
To: Jan Engelhardt <jengelh@medozas.de>
Cc: David Miller <davem@davemloft.net>,
stephen.hemminger@vyatta.com, netfilter-devel@vger.kernel.org
Subject: Re: iproute2: use automake
Date: Tue, 16 Nov 2010 07:58:51 -0800 [thread overview]
Message-ID: <20101116075851.0de8d177@nehalam> (raw)
In-Reply-To: <alpine.LNX.2.01.1011161108330.25859@obet.zrqbmnf.qr>
On Tue, 16 Nov 2010 11:09:06 +0100 (CET)
Jan Engelhardt <jengelh@medozas.de> wrote:
> On Tuesday 2010-11-16 02:59, David Miller wrote:
> >
> >> Not using something standardized is an affront to distributors,
> >> and the build instructions just a sore for the eye:
> >
> >Making the build take 10 times longer is more of an affront
> >than what you accuse iproute2 of doing.
> >
> >Please do not do this, I absolutely hate working on source
> >trees that use this crap!
> >
> If you like cmake or another build system better, I'd have no problem
> with that.
Until you make a convincing case that the existing infrastructure
is a problem, choosing an alternative solution is bogus.
All the fancy build systems are designed to solve the issue
of building one piece of software in multiple environments.
The iproute2 utilities only work on Linux and so far I haven't
had any major complaints from any distribution maintainer about it.
--
next prev parent reply other threads:[~2010-11-16 15:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 22:23 iproute2: use automake Jan Engelhardt
2010-11-15 22:23 ` [PATCH 1/2] Fix up permissions on scripts Jan Engelhardt
2010-11-15 22:23 ` [PATCH 2/2] build: start using Automake for building Jan Engelhardt
2010-11-15 22:26 ` iproute2: use automake Stephen Hemminger
2010-11-15 22:30 ` Jan Engelhardt
2010-11-16 1:59 ` David Miller
2010-11-16 10:09 ` Jan Engelhardt
2010-11-16 15:58 ` Stephen Hemminger [this message]
2010-11-16 17:41 ` David Miller
2010-11-16 20:11 ` Jan Engelhardt
2010-11-16 20:12 ` Jan Engelhardt
2010-11-16 20:18 ` David Miller
2010-11-15 22:32 ` Eric Dumazet
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=20101116075851.0de8d177@nehalam \
--to=shemminger@vyatta.com \
--cc=davem@davemloft.net \
--cc=jengelh@medozas.de \
--cc=netfilter-devel@vger.kernel.org \
--cc=stephen.hemminger@vyatta.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 NNTP newsgroup(s).