All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Miller <davem@davemloft.net>
To: shemminger@vyatta.com
Cc: jengelh@medozas.de, stephen.hemminger@vyatta.com,
	netfilter-devel@vger.kernel.org
Subject: Re: iproute2: use automake
Date: Tue, 16 Nov 2010 09:41:32 -0800 (PST)	[thread overview]
Message-ID: <20101116.094132.59704380.davem@davemloft.net> (raw)
In-Reply-To: <20101116075851.0de8d177@nehalam>

From: Stephen Hemminger <shemminger@vyatta.com>
Date: Tue, 16 Nov 2010 07:58:51 -0800

> 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.

I totally agree.

I can't count the amount of times I've seen major source trees
invest tons of engineering into things to decrease the pain of
using things like automake and libtool.

X11 even has a script that basically turns libtool into one big
fat NOP, because on Linux everything libtool tries to figure out
is completely superfluous.

Don't crap up the tree with unnecessary non-sense just for some
theoretical gain.  Things work just fine right now.

  reply	other threads:[~2010-11-16 17:41 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
2010-11-16 17:41           ` David Miller [this message]
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=20101116.094132.59704380.davem@davemloft.net \
    --to=davem@davemloft.net \
    --cc=jengelh@medozas.de \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=shemminger@vyatta.com \
    --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 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.