public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ulrich Mueller <ulm@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: Ionen Wolkens <ionen@gentoo.org>
Subject: Re: [gentoo-dev] [PATCH 1/2] linux-info.eclass: Drop temporary fix for powerpc
Date: Tue, 02 Jul 2024 09:38:33 +0200	[thread overview]
Message-ID: <ucynwfdl2@gentoo.org> (raw)
In-Reply-To: <ZoORiGUKnEyfjj5x@eversor> (Ionen Wolkens's message of "Tue, 2 Jul 2024 01:35:04 -0400")

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

>>>>> On Tue, 02 Jul 2024, Ionen Wolkens wrote:

> On a side-note, it was further a no-op for linux-mod-r1 which opted to
> intentionally ignore BUILD_FIXES (variable is currently read by kernel-2
> and linux-mod-r0) and nobody complained.

> If wanted, technically all references of BUILD_FIXES could probably be
> removed from eclasses given (normally) nothing sets that variable beside
> that ppc workaround. It was also undocumented and more like a private
> variable.

> Albeit some ebuilds (like the pre-linux-mod-r1 lttng-modules ebuild)
> and users have wrongly used it, so it could break some spacebar heating.
> No real need to bother with linux-mod.eclass either way given it's due
> for eventual removal.

A follow-up patch removing the two remaining references to BUILD_FIXES
(in getfilevar(), both in linux-info.eclass and in kernel-2.eclass)
would be trivial. The variable was originally added by commit [1].

Any other opinions on this?

Ulrich

[1] https://gitweb.gentoo.org/archive/repo/gentoo-2.git/commit/?id=c3d67d556962a79e055053f7cb88c67c46df293f

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

  reply	other threads:[~2024-07-02  7:38 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-01 21:36 [gentoo-dev] [PATCH 1/2] linux-info.eclass: Drop temporary fix for powerpc Ulrich Müller
2024-07-01 21:36 ` [gentoo-dev] [PATCH 2/2] linux-info.eclass: Drop support for EAPI 6 Ulrich Müller
2024-07-02  5:35 ` [gentoo-dev] [PATCH 1/2] linux-info.eclass: Drop temporary fix for powerpc Ionen Wolkens
2024-07-02  7:38   ` Ulrich Mueller [this message]
2024-07-03 15:42     ` [gentoo-dev] [PATCH v2 1/4] " Ulrich Müller
2024-07-03 15:42       ` [gentoo-dev] [PATCH v2 2/4] linux-info.eclass: Drop support for EAPI 6 Ulrich Müller
2024-07-03 15:42       ` [gentoo-dev] [PATCH v2 3/4] linux-info.eclass: Drop reference to BUILD_FIXES variable Ulrich Müller
2024-07-03 15:42       ` [gentoo-dev] [PATCH v2 4/4] kernel-2.eclass: " Ulrich Müller

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=ucynwfdl2@gentoo.org \
    --to=ulm@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