From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id 1B4351382C5 for ; Sat, 24 Mar 2018 20:34:20 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 53405E07EA; Sat, 24 Mar 2018 20:34:13 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id 00502E07D4 for ; Sat, 24 Mar 2018 20:34:12 +0000 (UTC) Received: from katipo2.lan (unknown [203.86.205.69]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) (Authenticated sender: kentnl) by smtp.gentoo.org (Postfix) with ESMTPSA id 68B4E335C09 for ; Sat, 24 Mar 2018 20:34:11 +0000 (UTC) Date: Sun, 25 Mar 2018 09:33:40 +1300 From: Kent Fredric To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] New Portage fork: sys-apps/portage-mgorny Message-ID: <20180325093340.4237c829@katipo2.lan> In-Reply-To: <7f211ecf-a415-b91a-25fb-6cb1b456a8ca@gentoo.org> References: <1521745426.836.25.camel@gentoo.org> <20180322214732.GA4096@eddy> <1521756383.23424.0.camel@gentoo.org> <23220.52565.280134.566970@a1i15.kph.uni-mainz.de> <0559e21f-edcb-986f-0a0b-1bc54bc169a6@gmail.com> <23220.56500.47110.798699@a1i15.kph.uni-mainz.de> <20180324200239.24cde39f@katipo2.lan> <1521878540.1070.0.camel@gentoo.org> <20180324220114.748273c5@katipo2.lan> <7f211ecf-a415-b91a-25fb-6cb1b456a8ca@gentoo.org> Organization: Gentoo X-Mailer: Claws Mail 3.15.1-dirty (GTK+ 2.24.31; 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-sha256; boundary="Sig_/jV2KDO1sB/Em.JjcObqEEiz"; protocol="application/pgp-signature" X-Archives-Salt: 3750b57b-b944-4edc-888d-fd18a62b836f X-Archives-Hash: 0e74664fd921d5e01da8a0987336d63f --Sig_/jV2KDO1sB/Em.JjcObqEEiz Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: quoted-printable On Sat, 24 Mar 2018 11:27:20 -0700 Zac Medico wrote: > The defaults certainly do not work perfectly in all situations. However, > there are a vast number of situations where using --autounmask-continue > will make appropriate package.mask changes without the need for any user > intervention. Its really handy for use flags. Its really handy for mixed arch/~arch where it promotes arch to ~arch as ne= eded. Its really really bad however to have a default of accepting ** and package.unmask as a primary go-to solution. That default gets people using broken openssl and experimental packages blindly without them ever having intended on getting into experimental waters. --Sig_/jV2KDO1sB/Em.JjcObqEEiz Content-Type: application/pgp-signature Content-Description: OpenPGP digital signature -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEPZazbI/qrFT1o9rn6FQySxNmqCAFAlq2tjEACgkQ6FQySxNm qCA2LQ/+IFMSk7+M7dcMq9vuGlYE2JxnGNnUR8R0OV2cGEyat/6UzcARnM4DtD+d 7gbTFrPKweIsUNgm4J71zthKsFWxHwjc0V9GsGDzeCWli7/Isp2iBtDvM6PxshjS YF4Yiz9ubexlFGWiC4HcgKdwcLpW+vCoLm82RCPXz/OZoQGBdJwmHxACHyUrbQb3 M+lUmemw5dnV8XjhQCtKIRcT1ttRg2eNHIHxrBir4Ue1CsxQyWGBG9zt4v9XWbtK 837KUxyM2gk6yP//7mBSX3FeEyv86AdIKlCAR+lTLOJfe+O9bpN+hE3aMGjBB3qc L1FGR7B93HIxGrGratSw0FkOMKFlZuKdKcYgqC9HznQjGA9L/soQsSgkE/l1wFB9 mndSip5fgFp4Btg7id6Kj5Jhy1Cgj1F9G+l2M/Uad5Q86+StFrK66YBU8qJIobbw JyS2fjgcjqOdjsr+GldaBIrrJrbQWW5n8UVUJhyLrq0sZ/DtVrBrh+tMGMxe/pY3 v7YfBidNkXl4qsggkjLnv1KMELBPE2fG3J/p9fP8a3gde4g4liQZqxtIXP1Tn27Y vd+j5J8UnxdH23dPSn6s/RTHg/eLqSHwzJf7vhY9/8GXaT21raBfeNT8fsfUY7mG lnaOEn1TPhlP3Jvfg8x4pY3RRtQ4xthCAQ4TwyqYvKhU9mwshoo= =MVS3 -----END PGP SIGNATURE----- --Sig_/jV2KDO1sB/Em.JjcObqEEiz--