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, Ionen Wolkens <ionen@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH v3 0/1] greadme.eclass: new eclass
Date: Thu, 13 Jun 2024 14:53:31 +0200	[thread overview]
Message-ID: <914fbd78-11b9-462c-86f4-9b89bb566166@gentoo.org> (raw)
In-Reply-To: <ZmrfI2U0ZuXbQC3t@eversor>

On 13/06/2024 13.59, Ionen Wolkens wrote:
> On Thu, Jun 13, 2024 at 10:39:24AM +0200, Florian Schmaus wrote:
>> 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).
> 
> I don't recall requesting anything, or was it something i said on
> IRC that I forgot about?

No, that seems to be a misunderstanding then. You wrote about the 
maintainer being able to choose when the readme is worth showing again 
and that a comparison would also "display it for minor style or typo
fixes.".

I thought that this was asking for a manual override. I am sorry, seems 
that I got that wrong.


> Also I assume GREADME_SHOW is actually GREADME_FORCE?

It's actually the other way around. Latest HEAD of greadme.eclass has

# @ECLASS_VARIABLE: GREADME_SHOW
# @DEFAULT_UNSET
# @DESCRIPTION:
# If set to "yes" then unconditionally show the contents of the readme
# file in pkg_postinst via elog. If set to "no", then do not show the
# contents of the readme file, even if they have changed.

- Flow


      reply	other threads:[~2024-06-13 12:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-06-13  8:39 [gentoo-dev] [PATCH v3 0/1] greadme.eclass: new eclass Florian Schmaus
2024-06-13  8:39 ` [gentoo-dev] [PATCH v3 1/1] " 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 [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=914fbd78-11b9-462c-86f4-9b89bb566166@gentoo.org \
    --to=flow@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=ionen@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