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.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by finch.gentoo.org (Postfix) with ESMTPS id C118D15802F for ; Fri, 31 Mar 2023 20:27:59 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 403EAE088C; Fri, 31 Mar 2023 20:27:56 +0000 (UTC) Received: from smtp.gentoo.org (dev.gentoo.org [IPv6:2001:470:ea4a:1:5054:ff:fec7:86e4]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by pigeon.gentoo.org (Postfix) with ESMTPS id F08CAE0884 for ; Fri, 31 Mar 2023 20:27:55 +0000 (UTC) References: <20230329153934.4053851-1-sam@gentoo.org> <88e081d7188b2764e69a1c471410b20ea106c45c.camel@gentoo.org> User-agent: mu4e 1.8.14; emacs 29.0.60 From: Sam James To: gentoo-dev@lists.gentoo.org Cc: Hans de Graaff Subject: Re: [gentoo-dev] [PATCH 1/3] ruby-ng.eclass: improve error when no valid Ruby in USE_RUBY Date: Fri, 31 Mar 2023 21:27:31 +0100 In-reply-to: <88e081d7188b2764e69a1c471410b20ea106c45c.camel@gentoo.org> Message-ID: <87r0t4wtrs.fsf@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 X-Auto-Response-Suppress: DR, RN, NRN, OOF, AutoReply MIME-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha512; protocol="application/pgp-signature" X-Archives-Salt: 64b51a90-0df9-4467-86b3-5f1825cfe4bb X-Archives-Hash: dfe2d96fd629484b04be1bef56cf89f3 --=-=-= Content-Type: text/plain Hans de Graaff writes: > [[PGP Signed Part:Undecided]] > On Wed, 2023-03-29 at 16:39 +0100, Sam James wrote: >> This means we don't get confusing *DEPEND/REQUIRED_USE errors about >> it being >> unparseable and instead just get a straightforward die message >> indicating >> the problem. > > > All three patches look good to me. Thanks! I'm going to rework the IUSE test stuff based on the feedback as it's apparently fragile to do at all. > > Hans > > [[End of PGP Signed Part]] --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iOUEARYKAI0WIQQlpruI3Zt2TGtVQcJzhAn1IN+RkAUCZCdCR18UgAAAAAAuAChp c3N1ZXItZnByQG5vdGF0aW9ucy5vcGVucGdwLmZpZnRoaG9yc2VtYW4ubmV0MjVB NkJCODhERDlCNzY0QzZCNTU0MUMyNzM4NDA5RjUyMERGOTE5MA8cc2FtQGdlbnRv by5vcmcACgkQc4QJ9SDfkZCdHgD9HEEQMojeFd/xwRJ2lLuePS6wSeRTCB0pb4pc g5JHUwUA/0jlz2VMxFBYqu/PWmnATr2iWiYwr0aST5ny3Vv10ecD =OGLD -----END PGP SIGNATURE----- --=-=-=--