From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.60) (envelope-from ) id 1SkTif-0002Ol-Lv for garchives@archives.gentoo.org; Fri, 29 Jun 2012 05:26:13 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 4942BE0763; Fri, 29 Jun 2012 05:26:05 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id 5E171E0653 for ; Fri, 29 Jun 2012 05:25:30 +0000 (UTC) Received: from vapier.localnet (localhost [127.0.0.1]) by smtp.gentoo.org (Postfix) with ESMTP id CE0A31B404D for ; Fri, 29 Jun 2012 05:25:29 +0000 (UTC) From: Mike Frysinger Organization: wh0rd.org To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] My wishlist for EAPI 5 Date: Fri, 29 Jun 2012 01:25:32 -0400 User-Agent: KMail/1.13.7 (Linux/3.4.0; KDE/4.6.5; x86_64; ; ) References: <4FE231BA.6020404@gentoo.org> In-Reply-To: <4FE231BA.6020404@gentoo.org> 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; boundary="nextPart1609985.XtU5RNuNmz"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <201206290125.33488.vapier@gentoo.org> X-Archives-Salt: b44c54f5-9019-44ba-bb79-0c0855a8e585 X-Archives-Hash: 9100a3dc4db78a701a062e958bc6d818 --nextPart1609985.XtU5RNuNmz Content-Type: Text/Plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable On Wednesday 20 June 2012 16:25:30 Richard Yao wrote: > Multilib (and/or multiarch) support Thomas already has multilib documents put together for review. multiarch=20 doesn't make sense for us, and even if it did, there's no way it'd be spec-= ed=20 out in a reasonable time frame for EAPI=3D5 (or even 6 or 7 or ...). > The current binaries cause a great deal of pain, particularly when a > user does not want to upgrade something. I had this problem with WINE > and glibc because I wanted to avoid the reverse memcpy() fiasco on my > systems. This situation would have been avoided entirely if the package > manager supported multilib. i don't buy this argument and makes me think when you say "multilib", you=20 don't actually mean "multilib". > Automated epatch_user support > Users should be able to test patches without modifying their ebuilds. > This also saves developer time because we don't need to navigate the > portage tree (or an overlay), make a change and test it. We could just > dump the patch in the appropriate directory and build. putting forth an idea is one thing. working out the technical aspects is=20 different. this sounds like something destined for EAPI=3D6: currently,=20 epatch_user uses epatch, and that provides a lot of dynamic patch support t= hat=20 doesn't fit well with being spec-ed out / encoded in PMS. > Parallel make checks SGTM > POSIX Shell compliance > There has been a great deal of work done to give the user full control > of what is on his system and there is more that we can do there. In > particular, I think a lean Gentoo Linux system should be able to use > busybox sh and nothing else. That requires POSIX shell compliance. > OpenRC init scripts support this and the configure scripts support this. > The few exceptions are bugs that are addressed by the Gentoo BSD > developers. As such, I think we should make EAPI=3D5 use POSIX shell by > default. If an ebuild requires bash, we can allow the ebuild to declare > that (e.g. WANT_SH=3Dbash), but that should be the exception and not the > rule. not a chance, and your logic about "choice" really makes no sense in the=20 ebuild context. read the archives wrt Roy Maples (sadly) burning out for i= n- depth details as to why this is a no-go. =2Dmike --nextPart1609985.XtU5RNuNmz Content-Type: application/pgp-signature; name=signature.asc Content-Description: This is a digitally signed message part. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.17 (GNU/Linux) iQIcBAABAgAGBQJP7TxNAAoJEEFjO5/oN/WBwm0P/0eb5LewG2Qhx2Oknz3w1KH1 igkrq/LMgB2fGzji1KGZvMdekJvFajoWJ6bfi8zFC7qjWPQ9KXHzWiJtOyZL0ADH yp7IvrT2NhJkyDTx8lhwbSqRFyLZjn6Sid7nLlgaNlxIYvLsURfADm/b5yx3CvpE mJipluS5WEhvx4jPomn1Jx7trk0Klv8U/CaBi7MLi4vRO2V+pkZuzy9OVL1O1tBJ iofnbj+EDYZ/wdedNw0Ws6VNAPdJEKRC6t10xcA5NQIBbfD6SzKwJAMSHkP7Ft4M saJDbth2DMPl33cxqTCSlNaJHj6edTTxaZSj2h1z2CIw45sdhB/+HiX2JWzRPSjw uB2NcOzCGAiIqBqyxbC5dYTO72bVZSSh05a3wcbchB8IFWByEVWgs7c3iwDTmaDj eu0fXSDa4ircMbB68HFqk2n6oouyHP3Gb+NhI8Ps5uILzWKHJhOTqxMzBwwalJlR YvKJTNrzjsfzCn51RVJMtLjCoeABEQ/4V13O19fJTiHtrx95hDu2DWgBsdfr+Lw/ f9NPCFifHmkERUnXPPUD2o+dPqM+vk073+D+wjXB52GhTUNkEURLJ4nl2JiWZC1E EEnDaai0db8tBU7G9Q15RqjVkd6nLKA5XZZFc3hfLgnoDXfDG3K05/WDh0JSRXr2 MdlM1BWc5TeG8sTzfvtU =T+CI -----END PGP SIGNATURE----- --nextPart1609985.XtU5RNuNmz--