Re: [PATCH] Add a custom ./configure script

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Dear diary, on Tue, Jul 04, 2006 at 03:50:16PM CEST, I got a letter
where Jakub Narebski <jnareb@xxxxxxxxx> said that...
> Petr Baudis wrote:
> 
> > The patch is on top of pu, that is Jakub Narebski's autoconf patch, because
> > it reuses most of its infrastructure and just replaces the configure script.
> 
> 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.

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

-- 
				Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
Snow falling on Perl. White noise covering line noise.
Hides all the bugs too. -- J. Putnam
-
: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]