From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org, "Michał Górny" <mgorny@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH] cargo.eclass: Optimize crate unpacking
Date: Mon, 13 May 2024 16:00:31 +0200 [thread overview]
Message-ID: <f35584f5-7c0a-4466-b8f7-f76a345178fb@gentoo.org> (raw)
In-Reply-To: <849a540bd028ac0fed47c75c71ecf077f703c28d.camel@gentoo.org>
On 12/05/2024 20.21, Michał Górny wrote:
> On Sun, 2024-05-12 at 19:22 +0200, Florian Schmaus wrote:
>> On 12/05/2024 04.26, Michał Górny wrote:
>>> + if [[ ${PKGBUMPING} != ${PVR} ]]; then
>>> + pushd "${DISTDIR}" >/dev/null || die
>>> +
>>> + ebegin "Unpacking crates"
>>> + printf '%s\0' "${crates[@]}" |
>>> + xargs -0 -P "$(makeopts_jobs)" -n 1 -- \
>>
>> Consider using get_makeopts_jobs instead of makeopts_jobs, as it
>> searches more variables for --jobs.
>
> Whose bright idea was to add a second similarly named function that does
> roughly the same thing but apparently differently? It can hardly get
> more confusing.
You are absolutely right, it sucks that we have two very similar methods.
You are invited to suggest how the situation can be improved. However,
rambling without presenting alternatives is not helpful in any way.
Potentially, you will either discover that there is a reason why things
are the way they are, or find a better solution.
- Flow
next prev parent reply other threads:[~2024-05-13 14:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-12 2:26 [gentoo-dev] [PATCH] cargo.eclass: Optimize crate unpacking Michał Górny
2024-05-12 2:44 ` Sam James
2024-05-12 17:22 ` Florian Schmaus
2024-05-12 18:21 ` Michał Górny
2024-05-13 14:00 ` Florian Schmaus [this message]
2024-05-13 14:02 ` Michał Górny
2024-05-16 6:55 ` [gentoo-dev] Obtaining values for --jobs and --load-average Florian Schmaus
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=f35584f5-7c0a-4466-b8f7-f76a345178fb@gentoo.org \
--to=flow@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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