Gentoo Archives: gentoo-dev

From: "Marcus D. Hanwell" <cryos@g.o>
To: gentoo-dev@l.g.o
Subject: Re: [gentoo-dev] [RFC] Ability to pass arguments to src_configure/src_compile
Date: Sun, 07 Sep 2008 16:46:50
Message-Id: 48C40575.6030202@gentoo.org
In Reply to: Re: [gentoo-dev] [RFC] Ability to pass arguments to src_configure/src_compile by Ciaran McCreesh
1 Ciaran McCreesh wrote:
2 > On Sun, 7 Sep 2008 17:31:37 +0200 (CEST)
3 > Vaeth <vaeth@××××××××××××××××××××××××.de> wrote:
4 >
5 >> Santiago M. Mola wrote:
6 >>
7 >>> Alec Warner <antarus@g.o> wrote:
8 >>>
9 >>>> Thomas Anderson <gentoofan23@g.o> wrote:
10 >>>>
11 >>>>> DEFAULT_SRC_CONFIGURE_USE_{WITHS,ENABLES}
12 >>>>> DEFAULT_SRC_CONFIGURE_EXTRA_PARAMS
13 >>>>>
14 >> Essentially, this is the suggestion to replace the flexible shell code
15 >> by some static variables. Besides being less intuitive and less
16 >> readable (you have to know the meaning of all the variables to
17 >> understand it) it also works only for fixed cases, e.g. if it is
18 >> only ./configure (and not ./autogen.sh or something else) which has
19 >> to be called, and only if it has to be called exactly once in the
20 >> main directory For all other cases, either *everything* has to be
21 >> done manually, or you have to introduce even more variables to cover
22 >> more cases.
23 >>
24 >
25 > The proposal is not designed to replace all cases. It's designed to
26 > replace the common 50%.
27 >
28 I personally agree with several others who have replied to this thread.
29 The reduction in lines of code/characters seems to introduce an uglier
30 syntax which is harder to read with questionable benefits.

Replies

Subject Author
Re: [gentoo-dev] [RFC] Ability to pass arguments to src_configure/src_compile Ciaran McCreesh <ciaran.mccreesh@××××××××××.com>
Re: [gentoo-dev] [RFC] Ability to pass arguments to src_configure/src_compile Donnie Berkholz <dberkholz@g.o>