public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arthur Zamarin <arthurzam@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Sam James <sam@gentoo.org>
Subject: Re: [gentoo-dev] Re: [PATCH] ruby-utils.eclass: Simplify _ruby_implementation_depend
Date: Fri, 14 Jul 2023 19:19:18 +0300	[thread overview]
Message-ID: <48968b07-9cf6-a867-7c71-d1920f16ead8@gentoo.org> (raw)
In-Reply-To: <877cr228h9.fsf@gentoo.org>


[-- Attachment #1.1: Type: text/plain, Size: 887 bytes --]

On 14/07/2023 11.37, Sam James wrote:
> 
> Sam James <sam@gentoo.org> writes:
> 
>> From: konsolebox <konsolebox@gmail.com>
>>
>> Closes: https://bugs.gentoo.org/909529
>> Signed-off-by: Sam James <sam@gentoo.org>
> 
> ftr, while I find the case really repetitive, I'm not sure if this
> crosses the line into unreadable bash or not, so I feel on the fence.
> 
> But I wanted it reviewed on ML in any case, rather than us forgetting
> it on BZ.
> 

I agree the code isn't easy to read, but it isn't too hard. I do want to
suggest you add a simple comment on the same line bringing an example
value for the rubyslot. With an example comment, it becomes trivial to
understand (and if someone needs to change it, he know beforehand what
format to expect).

-- 
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Python, pkgcore stack, Arch Teams, GURU)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

      parent reply	other threads:[~2023-07-14 16:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-14  8:34 [gentoo-dev] [PATCH] ruby-utils.eclass: Simplify _ruby_implementation_depend Sam James
2023-07-14  8:37 ` [gentoo-dev] " Sam James
2023-07-14 16:16   ` Hans de Graaff
2023-07-14 16:19   ` Arthur Zamarin [this message]

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=48968b07-9cf6-a867-7c71-d1920f16ead8@gentoo.org \
    --to=arthurzam@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=sam@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