Re: [PATCH] Add a custom ./configure script
- From
Alex Riesen <raa.lkml@gmail.com>
- Date
- Jul 5, 2006, 16:46 UTC
- Message-ID
- <81b0412b0607050946y34bf28d5gca30264375fb7957@mail.gmail.com>
- In-Reply-To
- <20060704215747.GQ29115@pasky.or.cz>
On 7/4/06, Petr Baudis <pasky@suse.cz> wrote:
Show 8 quoted lines
> > > > 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.