public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Florian Schmaus <flow@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: pacho@gentoo.org, Florian Schmaus <flow@gentoo.org>
Subject: [gentoo-dev] [PATCH v3 0/1] greadme.eclass: new eclass
Date: Thu, 13 Jun 2024 10:39:24 +0200	[thread overview]
Message-ID: <20240613083928.165509-1-flow@gentoo.org> (raw)

Following up on the discussion of the last patchset, this
- moves the functionally into a new eclass, as adjusting the existing
  eclass to export new phase functions is not viable.
- excludes the README.gentoo from decompression, as all other
  presented approaches add complexity and cause additional disk space
  consumption. While on the other hand, README.gentoo files are
  typically very small because they should be suitable as pkg_postinst
  output, so ther is often not much gained by compressing them.
- adds a GREADME_SHOW show option, to manually override the behavior
  (as requested by ionen).

Note that I choose greadme.eclass as the name for the new eclass for
aesthetic reasons. I find readme.gentoo-r2 a mouthful, and it leads to
an ugly combination of dot, hyphen, and underscores. However, if
anyone wants to have function names like
'readme.gentoo-r2_pkg_postinst', then we can go with that.

Florian Schmaus (1):
  greadme.eclass: new eclass

 eclass/greadme.eclass | 223 ++++++++++++++++++++++++++++++++++++++++++
 1 file changed, 223 insertions(+)
 create mode 100644 eclass/greadme.eclass

-- 
2.44.2



             reply	other threads:[~2024-06-13  8:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  8:39 Florian Schmaus [this message]
2024-06-13  8:39 ` [gentoo-dev] [PATCH v3 1/1] greadme.eclass: new eclass Florian Schmaus
2024-06-13  9:31   ` Ulrich Mueller
2024-06-13  9:48     ` Ulrich Mueller
2024-06-13 10:18     ` Florian Schmaus
2024-06-13 10:42       ` Ulrich Mueller
2024-06-13 10:57         ` Florian Schmaus
2024-06-13 11:59 ` [gentoo-dev] [PATCH v3 0/1] " Ionen Wolkens
2024-06-13 12:53   ` 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=20240613083928.165509-1-flow@gentoo.org \
    --to=flow@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=pacho@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