From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Eray Aslan <eras@gentoo.org>
Subject: Re: [gentoo-dev] EGO_SUM (was: [gentoo-project] Gentoo Council Election 202306 ... Nominations Open in Just Over 24 Hours.)
Date: Mon, 3 Jul 2023 12:17:09 +0200 [thread overview]
Message-ID: <52703145-a284-30f3-aac8-69ed086a5f4a@gentoo.org> (raw)
In-Reply-To: <ZJ69pe-ZckIfqbWN@rog.a21an.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 832 bytes --]
On 30/06/2023 13.33, Eray Aslan wrote:
> On Fri, Jun 30, 2023 at 03:38:11AM -0600, Tim Harder wrote:
>> Why do we have to keep exporting the related variables that generally
>> cause these size issues to the environment?
>
> I really do not want to make a +1 response but this is an excellent
> question that we need to answer before implementing EGO_SUM.
Could you please discuss why you make the reintroduction of EGO_SUM
dependent on this question?
Portage will show you a warning message if the exported environment
approaches the kernel limit, and it will show a detailed error message
if executing an ebuild failed due to the limit being reached. There
seems to be no reason why you should not be able to allow EGO_SUM again
without first fixing, for example, https://bugs.gentoo.org/721088.
- Flow
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17273 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2023-07-03 10:17 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2ZKWN4KF.MKEFFMWE.LGPKYP47@RTL7EJXF.RN4PF6UF.MDFBGF3C>
[not found] ` <be450641-94ff-a0d9-51da-3a7a3abcc6c7@gentoo.org>
[not found] ` <b7309a3f-2980-b390-a16a-0518cce1da75@gentoo.org>
[not found] ` <87y1k33aoy.fsf@gentoo.org>
2023-06-30 8:15 ` [gentoo-dev] EGO_SUM (was: [gentoo-project] Gentoo Council Election 202306 ... Nominations Open in Just Over 24 Hours.) Florian Schmaus
2023-06-30 8:22 ` Sam James
2023-06-30 9:38 ` Tim Harder
2023-06-30 11:33 ` Eray Aslan
2023-07-03 10:17 ` Florian Schmaus [this message]
2023-07-04 7:13 ` Tim Harder
2023-07-04 10:44 ` Gerion Entrup
2023-07-04 21:56 ` Robin H. Johnson
2023-07-04 23:09 ` Oskari Pirhonen
2023-07-05 18:40 ` Gerion Entrup
2023-07-05 19:32 ` Rich Freeman
2023-07-06 2:48 ` Oskari Pirhonen
2023-07-06 6:09 ` Zoltan Puskas
2023-07-06 19:46 ` [gentoo-dev] EGO_SUM (was: [gentoo-project] Gentoo Council Election 202306 ... Nominations Open Hank Leininger
2023-07-08 20:49 ` [gentoo-dev] EGO_SUM (was: [gentoo-project] Gentoo Council Election 202306 ... Nominations Open in Just Over 24 Hours.) Sam James
2023-07-03 10:17 ` Florian Schmaus
2023-07-03 11:12 ` [gentoo-dev] EGO_SUM Ulrich Mueller
2023-07-08 21:21 ` [gentoo-dev] EGO_SUM (was: [gentoo-project] Gentoo Council Election 202306 ... Nominations Open in Just Over 24 Hours.) Sam James
[not found] ` <cdf5ddb7-8f65-74cf-5594-3e3eec86c915@gentoo.org>
[not found] ` <1913d3c2-5f54-acea-0ed3-930371ea1884@gentoo.org>
[not found] ` <CAAr7Pr9+zq2NV=7zhj5e+4LWOmNavCrfMstNTqkthk5uxQVNtg@mail.gmail.com>
2023-07-14 7:14 ` [gentoo-dev] Re: Flow's Manifesto and questions for nominees (was: " Florian Schmaus
2023-07-14 7:33 ` Sam James
2023-07-14 8:19 ` Sam James
2023-07-14 9:07 ` Florian Schmaus
2023-07-14 8:39 ` [gentoo-dev] Re: Flow's Manifesto and questions for nominees Ulrich Mueller
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=52703145-a284-30f3-aac8-69ed086a5f4a@gentoo.org \
--to=flow@gentoo.org \
--cc=eras@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox