From: Florian Schmaus <flow@gentoo.org>
To: Ulrich Mueller <ulm@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org, Arthur Zamarin <arthurzam@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH v4] greadme.eclass: new eclass
Date: Wed, 19 Jun 2024 14:18:11 +0200 [thread overview]
Message-ID: <055e2438-c187-49de-946f-8f2d9d714292@gentoo.org> (raw)
In-Reply-To: <ued8tpc2z@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 844 bytes --]
On 19/06/2024 10.32, Ulrich Mueller wrote:
>>>>>> On Tue, 18 Jun 2024, Florian Schmaus wrote:
>
>> Any preference regarding the auto-formatting tool? The
>> readme.gentoo-r1.eclass uses fold, but fmt (both are in coreutils)
>> would probably also be an option (and has a --uniform-spacing option
>> ;)).
>
> readme.gentoo.eclass originally had fmt, but then switched to fold
> following discussion in bug 460050 [1].
'fold' it is then. See
https://gitlab.com/flow/flow-s-ebuilds/-/commit/a9215c903a5434a65df1f2cae8409750d94eec74
Note that thanks to greadme.eclass *not* using a variable like
DOC_CONTENTS, we can avoid some shell trickery that
readme.gentoo-r1.eclass has to do [1].
- Flow
1:
https://github.com/gentoo/gentoo/blob/f10decf0ec3bdf75618124534057df0a14b8c61b/eclass/readme.gentoo-r1.eclass#L63-L68
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 17797 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 618 bytes --]
next prev parent reply other threads:[~2024-06-19 12:18 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 ` [gentoo-dev] " Duncan
2024-06-18 11:33 ` [gentoo-dev] " 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 [this message]
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=055e2438-c187-49de-946f-8f2d9d714292@gentoo.org \
--to=flow@gentoo.org \
--cc=arthurzam@gentoo.org \
--cc=gentoo-dev@lists.gentoo.org \
--cc=ulm@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