From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH 1/7] eclass/nuget.eclass: introduce new eclass
Date: Sun, 30 Jul 2023 22:19:59 +0200 [thread overview]
Message-ID: <3293c666-6d3c-8aaf-37f7-35020bd3decf@gentoo.org> (raw)
In-Reply-To: <4766db0bfe4ba2b55d74034f83608b8461145808.camel@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 1784 bytes --]
On 30/07/2023 21.30, Michał Górny wrote:
> On Sun, 2023-07-30 at 16:26 +0200, Maciej Barć wrote:
>> +# @FUNCTION: nuget_uris
>> +# @USAGE: <nuget...>
>> +# @DESCRIPTION:
>> +# Generates the URIs to put in SRC_URI to help fetch dependencies.
>> +# If no arguments provided, uses the "NUGETS" variable.
>
> Sounds like you're copying the old, horribly slow cargo.eclass API.
> Don't do that, unless you have to. Prefer variable-setting approach
> used by modern cargo.eclass.
Should we make this a policy then?
On the other hand, I also wonder if its worth it.
You gave a similar comment when reviewing gradle.eclass and you changed
the cargo.eclass to also provide the "variable-setting approach" [1].
However, while the $() construct in shells is relatively expensive due
to the involved forking, it is usually only harmful when used in loops
with a high iteration count. The loop in go-modules.eclass was a prime
example of this. The loop was later fixed [2], and I can not help to
think that this fix caused people to look for further usages of the fork
construct.
Providing a better UX by increasing performance is good. Nevertheless,
this should not become a which hunt.
The usage of cargo_carte_uris/ngutes_uris/gradle_src_uri is not in a
large loop, therefore the situation is not comparable with the one in
the go-modules.eclass [2].
Which problem are we solving by moving away from this towards a slightly
more verbose construct?
- Flow
1: 59dbfb80f748 ("cargo.eclass: Add variable alternative to
$(cargo_crate_uris)")
https://github.com/gentoo/gentoo/commit/59dbfb80f748
2: 45e7aecd81e0 ("go-module.eclass: inline _go-module_gomod_encode()")
https://github.com/gentoo/gentoo/commit/45e7aecd81e0
[-- 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-30 20:20 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-30 14:26 [gentoo-dev] [PATCH 1/7] eclass/nuget.eclass: introduce new eclass Maciej Barć
2023-07-30 14:26 ` [gentoo-dev] [PATCH 2/7] eclass/dotnet-pkg-utils.eclass: " Maciej Barć
2023-07-30 19:34 ` Michał Górny
2023-07-30 20:04 ` Maciej Barć
2023-07-31 5:09 ` Michał Górny
2023-07-30 14:26 ` [gentoo-dev] [PATCH 3/7] eclass/dotnet-pkg.eclass: " Maciej Barć
2023-07-31 9:20 ` Thomas Bracht Laumann Jespersen
2023-07-30 14:26 ` [gentoo-dev] [PATCH 4/7] dev-dotnet/dotnet-runtime-nugets: new package Maciej Barć
2023-07-30 14:26 ` [gentoo-dev] [PATCH 5/7] app-eselect/eselect-dotnet: " Maciej Barć
2023-07-30 14:26 ` [gentoo-dev] [PATCH 6/7] dev-dotnet/dotnet-sdk-bin: update packaging mechanism Maciej Barć
2023-07-30 14:26 ` [gentoo-dev] [PATCH 7/7] dev-dotnet/dotnet-sdk-bin: drop old Maciej Barć
2023-07-30 19:30 ` [gentoo-dev] [PATCH 1/7] eclass/nuget.eclass: introduce new eclass Michał Górny
2023-07-30 20:01 ` Maciej Barć
2023-07-31 5:08 ` Michał Górny
2023-07-30 20:19 ` Florian Schmaus [this message]
2023-07-31 5:02 ` Michał Górny
2023-07-31 7:53 ` Florian Schmaus
2023-07-31 9:32 ` Sam James
2023-07-31 10:49 ` Florian Schmaus
2023-07-31 11:39 ` Sam James
2023-07-31 13:53 ` Michał Górny
2023-07-31 14:20 ` Florian Schmaus
-- strict thread matches above, loose matches on Subject: below --
2023-07-16 12:38 Maciej Barć
2023-07-16 12:43 ` Sam James
2023-07-16 13:44 ` Maciej Barć
2023-07-16 13:40 ` Ulrich Mueller
2023-07-16 13:47 ` Maciej Barć
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=3293c666-6d3c-8aaf-37f7-35020bd3decf@gentoo.org \
--to=flow@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