Re: [PATCH 0/9] Introduce esplit.eclass and port to it

Sam James posted on Thu,  9 Jul 2026 22:22:09 +0100 as excerpted:

> Introduce a new eclass (esplit.eclass) and port ebuilds to it. This is
> needed to unblock a Portage release with sandboxing for the 'depend'
> phase enabled, because the uses of a heredoc replaced here always
> require a temporary file with < EAPI 9 (and with >= EAPI 9, they do but
> for large inputs only).

Just to ask, since "with >= EAPI 9" has unlimited scope that could be with 
us for awhile and the vagueness of "large" accordingly disturbs me...

Is it possible to better define "large" in "large inputs only"?

Are we talking "large" in terms of lines, characters, ...?  Is it on the 
order of 1K lines/characters?  Just 10 (hopefully lines in that case)? 
100K?  GiB size?

And should such justification be in the eclass (in-eclass documentation, 
or possibly just in the git commit comment) itself or is the series cover-
letter alone discoverable enough in terms of people "archaeologically" 
looking for the reason it was introduced, a decade or whatever from now?

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman