[gentoo-pms] Re: [gentoo-dev] [RFC] Shall econf append its arguments to end of ./configure invocation?

[Ulrich Mueller]

>>>>> On Tue, 30 Apr 2013, Ciaran McCreesh wrote:

> "Override" is a dodgy word, since we don't know how ./configure does.
> Specify how the arguments are passed, which we have control over, not
> how they behave.

See updated patch below.

> And it still needs Council approval...

That can be done.

Ulrich


From 31a2d63de1b8914063e82957e41de642d11eb092 Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Ulrich=20M=C3=BCller?= <ulm@g.o>
Date: Tue, 30 Apr 2013 14:59:15 +0200
Subject: [PATCH] econf arguments are passed after default options.

This matches long-time Portage behaviour, and for later added options
like --disable-dependency-tracking it follows the clarification given here:
http://archives.gentoo.org/gentoo-dev/msg_0189c554085ac8352b5a2e05647a1d97.xml
See also bug 406117.
---
 pkg-mgr-commands.tex | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/pkg-mgr-commands.tex b/pkg-mgr-commands.tex
index aa0c873..a70ffdb 100644
--- a/pkg-mgr-commands.tex
+++ b/pkg-mgr-commands.tex
@@ -136,7 +136,8 @@ has returned.
 \begin{description}
 \item[econf] Calls the program's \t{./configure} script. This is designed to work with GNU
     Autoconf-generated scripts. Any additional parameters passed to \t{econf} are passed directly
-    to \t{./configure}. \t{econf} will look in the current working directory for a configure script
+    to \t{./configure}, after the default options below.
+    \t{econf} will look in the current working directory for a configure script
     unless the \t{ECONF\_SOURCE} environment variable is set, in which case it is taken to be the
     directory containing it. \t{econf} must pass the following options to the configure script:
 
-- 
1.8.2.1