From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 5A3C91381F3 for ; Mon, 29 Apr 2013 05:56:12 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 46511E0AA1; Mon, 29 Apr 2013 05:56:05 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 66BF6E09AF for ; Mon, 29 Apr 2013 05:56:04 +0000 (UTC) Received: from localhost (178-37-178-225.adsl.inetia.pl [178.37.178.225]) (using SSLv3 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 933AD33BE0E; Mon, 29 Apr 2013 05:56:02 +0000 (UTC) Date: Mon, 29 Apr 2013 07:55:49 +0200 From: =?ISO-8859-2?B?TWljaGGzIEfzcm55?= To: Gentoo Developer Mailing List Subject: [gentoo-dev] [RFC] Shall econf append its arguments to end of ./configure invocation? Message-ID: <20130429075549.06e8ad66@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.9.0 (GTK+ 2.24.17; x86_64-pc-linux-gnu) Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org Mime-Version: 1.0 Content-Type: multipart/signed; micalg=PGP-SHA512; boundary="Sig_/omYYUhNV7leXnMKjqdNf2nt"; protocol="application/pgp-signature" X-Archives-Salt: 09f6d90c-4df1-4be1-b51e-7c5ee46677a3 X-Archives-Hash: d9760e07e123e65f7892a5d196db9567 --Sig_/omYYUhNV7leXnMKjqdNf2nt Content-Type: text/plain; charset=ISO-8859-2 Content-Transfer-Encoding: quoted-printable Hi, As you haven't expected at all, the PMS is a specific spec which doesn't document much of common sense. Therefore, the way econf is currently declared leaves the freedom of adding its arguments anywhere in the ./configure invocation [1]. By that, I mean that: econf --libdir=3D/lib could actually result in: ./configure --libdir=3D/lib ... --libdir=3D The only option guaranteed to be handled properly is --prefix which is directly processed by econf. Why I'm bringing this up? Because of bug #406117. Long story short, it's mostly about Ciaran having the imagination to let paludis pass ./configure arguments in semi-random order. As a result, default --disable-dependency-tracking goes after explicit --enable-dependency-tracking from the ebuild. Now, what are your thoughts? Shall we fix PMS to explicitly state the argument order or implement ugly hacks in ebuilds? [1]:http://dev.gentoo.org/~ulm/pms/5/pms.html#x1-13500011.3.3.7 [2]:https://bugs.gentoo.org/show_bug.cgi?id=3D406117 --=20 Best regards, Micha=B3 G=F3rny --Sig_/omYYUhNV7leXnMKjqdNf2nt Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iQJ8BAEBCgBmBQJRfgtlXxSAAAAAAC4AKGlzc3Vlci1mcHJAbm90YXRpb25zLm9w ZW5wZ3AuZmlmdGhob3JzZW1hbi5uZXQ1RUJGMjBGOTk2RkIzQzIyQ0M2RkNBNDBC QUJGMUQ1RkY4QzgxMTBBAAoJELq/HV/4yBEKkUcP/RmzAv+MnKRRWI/+LUhseTTO e74YV1i76EhvL+2KmuITpnw3PMXLalrTfoiU/C9kin7IEVVMXE/ZRxnh9FArgFcD w2piTpPVwwuClkyVH1uWSa5cS9NBHXOTDudwiXS/6ARl4o2sC6dZHC3Oeux8x5CY 4DwuwFgMw3KfASBs83BJhRtx0nsRZn22HffMdD86AXSHs0sdxntPFttgjL+yzPxP SPRkO6G7XDm5Fu3y6iJdo6XJidWKG8K+7448pEVzdQxliCKVTv+GRV6/0/YsCklO pQrt4yTjRWGOu4qptWWASAmgBeMiiZZQB4zl5y9QToGrjd2dLeE8AQ3pgNunkwoU 9Ue8hho+zobe8iLblSzehiq1lXuRhZ2yiD9quH5EhpQm4d6JKo9IktnaNm9UATQb ojL4C3xax0cdGFiGyTChME1kMIzVMATsjvkCsurW9LKsQWvPdOJJBiQs9tUOwp/h 3Is2VIHY3eFZTUbsj5ALyrFXBnMNu51G7grCObfLkIE2MUn/4S5enQsVbThi+ThD VUlNJuFW4uAlQ99/EwebbIQquSZNXMIF6A9gsYcoedd+OYVt6VTUn3sf0lGLgETX ugjza1bdDQXuTZl/DBdPWeyKnxws2XK8vSmVMa175kltryYfPOIUwH1E0HYFKQTb fOwwNYOgyOzSVMlx4ZqH =4qEI -----END PGP SIGNATURE----- --Sig_/omYYUhNV7leXnMKjqdNf2nt--