git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Alex Riesen" <raa.lkml@gmail.com>
To: "Petr Baudis" <pasky@suse.cz>
Cc: "Jakub Narebski" <jnareb@gmail.com>, git@vger.kernel.org
Subject: Re: [PATCH] Add a custom ./configure script
Date: Wed, 5 Jul 2006 18:46:43 +0200	[thread overview]
Message-ID: <81b0412b0607050946y34bf28d5gca30264375fb7957@mail.gmail.com> (raw)
In-Reply-To: <20060704215747.GQ29115@pasky.or.cz>

On 7/4/06, Petr Baudis <pasky@suse.cz> wrote:
> >
> > If you named it for example configure.sh, then autoconf generated version,
> > and your by hand created version could coexist.
>
> I'm not opposed to it per se, but I'm just not sure if it makes any
> sense to support them both in parallel, since then you have parallel
> infrastructure doing the exactly same thing, or worse yet - performing
> a subtly different set of tests. The benefit is unclear to me.

The benefit is on user side: he'll take what works for him, without waiting
for you or Jakub to fix it for him.

> Another thing is that it's named *everywhere* ./configure and if I use a
> different name now then it will be hard to rename.

but it not the same configure as "everywhere". It's your very own script.

That said, I like your script better than the autoconf thing.

  reply	other threads:[~2006-07-05 16:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-07-04  0:40 [PATCH] Add a custom ./configure script Petr Baudis
2006-07-04 13:50 ` Jakub Narebski
2006-07-04 21:57   ` Petr Baudis
2006-07-05 16:46     ` Alex Riesen [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-07-04  0:25 Petr Baudis

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=81b0412b0607050946y34bf28d5gca30264375fb7957@mail.gmail.com \
    --to=raa.lkml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.com \
    --cc=pasky@suse.cz \
    /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).