public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Sam James <sam@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: base-system@gentoo.org, "Ulrich Müller" <ulm@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH 1/3] autotools.eclass: Downgrade eqawarn for renaming configure.in
Date: Sun, 28 May 2023 14:36:58 +0100	[thread overview]
Message-ID: <87mt1ozidt.fsf@gentoo.org> (raw)
In-Reply-To: <20230528131641.13289-1-ulm@gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1418 bytes --]


Ulrich Müller <ulm@gentoo.org> writes:

> At this point, almost all upstreams will have switched to configure.ac.
> Therefore, configure.in is most likely an indication of an inactive
> upstream, and there is no useful way for the ebuild maintainer to
> silence the warning (other than the ebuild renaming the file).

Ionen's point was that such packages therefore regularly get updates
so a QA warning when rarely revbumping it isn't necessarily a problem either.

But I also don't think it's likely that upstream will ever actually
enforce this, so OK.

>
> Keep the message as einfo, so there is still an indication that the file
> was renamed.
>
> Bug: https://bugs.gentoo.org/426262
> Signed-off-by: Ulrich Müller <ulm@gentoo.org>
> ---
>  eclass/autotools.eclass | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/eclass/autotools.eclass b/eclass/autotools.eclass
> index 91046b9f82f3..3a040b863eea 100644
> --- a/eclass/autotools.eclass
> +++ b/eclass/autotools.eclass
> @@ -400,7 +400,7 @@ eautoconf() {
>  		*)
>  				# Move configure file to the new location only on newer EAPIs to ensure
>  				# checks are done rather than retroactively breaking ebuilds.
> -				eqawarn "Moving configure.in to configure.ac (bug #426262)"
> +				einfo "Moving configure.in to configure.ac (bug #426262)"
>  				mv configure.{in,ac} || die
>  			;;
>  		esac


[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 377 bytes --]

  parent reply	other threads:[~2023-05-28 13:37 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-05-28 13:16 [gentoo-dev] [PATCH 1/3] autotools.eclass: Downgrade eqawarn for renaming configure.in Ulrich Müller
2023-05-28 13:16 ` [gentoo-dev] [PATCH 2/3] autotools.eclass: Allow running the tools only in src_prepare Ulrich Müller
2023-05-28 13:38   ` Sam James
2023-05-28 13:16 ` [gentoo-dev] [PATCH 3/3] autotools.eclass: Whitespace Ulrich Müller
2023-05-28 13:36 ` Sam James [this message]
2023-05-28 13:44 ` [gentoo-dev] [PATCH 1/3] autotools.eclass: Downgrade eqawarn for renaming configure.in Pacho Ramos

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=87mt1ozidt.fsf@gentoo.org \
    --to=sam@gentoo.org \
    --cc=base-system@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