From: | Ciaran McCreesh <ciaran.mccreesh@××××××××××.com> | ||
---|---|---|---|
To: | gentoo-dev@l.g.o | ||
Subject: | Re: [gentoo-dev] [RFC] Shall econf append its arguments to end of ./configure invocation? | ||
Date: | Mon, 29 Apr 2013 21:00:02 | ||
Message-Id: | 20130429215950.019cd23b@googlemail.com | ||
In Reply to: | Re: [gentoo-dev] [RFC] Shall econf append its arguments to end of ./configure invocation? by Ulrich Mueller |
1 | On Mon, 29 Apr 2013 22:53:30 +0200 |
2 | Ulrich Mueller <ulm@g.o> wrote: |
3 | > > As you can see in the bug, we're not discussing anything related to |
4 | > > EAPI 0 behaviour, so this argument is irrelevant. We're discussing a |
5 | > > change in a later EAPI, where the change had nothing to say about |
6 | > > ordering. |
7 | > |
8 | > In the discussions that led to inclusion of the feature in EAPI 4, it |
9 | > was implicit that it would be possible to override the default. This |
10 | > can only work if "$@" goes after all default options. |
11 | |
12 | But that wasn't got approved by the Council... |
13 | |
14 | -- |
15 | Ciaran McCreesh |
File name | MIME type |
---|---|
signature.asc | application/pgp-signature |
Subject | Author |
---|---|
Re: [gentoo-dev] [RFC] Shall econf append its arguments to end of ./configure invocation? | Ulrich Mueller <ulm@g.o> |