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 9DF6B158089 for ; Wed, 13 Sep 2023 13:10:48 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 7B81D2BC17F; Wed, 13 Sep 2023 13:10:44 +0000 (UTC) Received: from smtp.gentoo.org (woodpecker.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 4250A2BC058 for ; Wed, 13 Sep 2023 13:10:44 +0000 (UTC) Message-ID: <5e1996ebadf6bb3f0c49509bda63a703744d1099.camel@gentoo.org> Subject: Re: [gentoo-dev] [PATCH 1/2] distutils-r1.eclass: teach setuptools to respect (some) build options From: Michael Orlitzky To: gentoo-dev@lists.gentoo.org Date: Wed, 13 Sep 2023 09:10:37 -0400 In-Reply-To: <3b8c01be-2ac6-8594-e841-fbbff9ea1ec4@gmail.com> References: <20230912191501.536700-1-eschwartz93@gmail.com> <1affddb8-221c-4c67-4395-03c2425d0e0e@gmail.com> <39ec5b95f8af61cc9e580b8f98cf8ce01b728d14.camel@gentoo.org> <3b8c01be-2ac6-8594-e841-fbbff9ea1ec4@gmail.com> Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable User-Agent: Evolution 3.48.4 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 X-Archives-Salt: 72364fea-6524-4483-8fe3-7ae8b08ff24d X-Archives-Hash: 6975b02340c915d89e7d14e2f918b642 On Tue, 2023-09-12 at 22:52 -0400, Eli Schwartz wrote: >=20 > Is portage generally expected to successfully complete (including > internal metadata write stages) when its workdir drive runs out of space > partway through? >=20 No, but I think what everyone else is forgetting to mention is that if it's going to fail, we want it to fail as soon as possible, i.e. as close to the thing that actually went wrong. If we proceed past ENOSPC or whatever, we could get five or six lines further in the ebuild, and then some other command will fail but possibly with a crazy unrelated error message.