From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: [PATCH v4] greadme.eclass: new eclass
Date: Mon, 17 Jun 2024 00:51:48 -0000 (UTC) [thread overview]
Message-ID: <pan$bb01b$8e9ff6d0$1d5a3b93$90c3b39@cox.net> (raw)
In-Reply-To: 45bcb8d5-bea7-49a2-81e8-ee2d161872bc@gentoo.org
Arthur Zamarin posted on Sun, 16 Jun 2024 21:15:25 +0300 as excerpted:
> On 16/06/2024 18.51, Florian Schmaus wrote:
>> This new eclass includes various improvements over the existing
>> readme.gentoo-r1.eclass.
>
> So, some weird question from me - why is it called greadme? I can
> understand why you don't want to modify existing eclass, but why not
> call it "readme.gentoo-r2.eclass"? This should make it a little less
> confusing (cause I imagine folks asking - which to use. With -r2 we all
> know which one is better).
I had the same question but it was answered to my satisfaction in
[PATCH v3 0/1]. Quoting from that:
>>> [I]f anyone wants to have function names like
>>> 'readme.gentoo-r2_pkg_postinst', then we can go with that.
Convinced me! greadme's /just/ fine, thankyou! =:^)
(Tho purely bikeshedding I'd prefer g2readme or gen2readme. Which FWIW
would match my gentoo bug shortcut g2b/g2bug...)
--
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
next prev parent reply other threads:[~2024-06-17 0:51 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-16 15:51 [gentoo-dev] [PATCH v4] greadme.eclass: new eclass Florian Schmaus
2024-06-16 18:15 ` Arthur Zamarin
2024-06-17 0:51 ` Duncan [this message]
2024-06-18 11:33 ` Florian Schmaus
2024-06-18 14:02 ` Ulrich Mueller
2024-06-18 14:53 ` Florian Schmaus
2024-06-18 18:21 ` Arthur Zamarin
2024-06-18 18:55 ` Ionen Wolkens
2024-06-18 20:48 ` Florian Schmaus
2024-06-19 8:32 ` Ulrich Mueller
2024-06-19 12:18 ` Florian Schmaus
2024-06-16 20:09 ` 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='pan$bb01b$8e9ff6d0$1d5a3b93$90c3b39@cox.net' \
--to=1i5t5.duncan@cox.net \
--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