Hi Florian, Florian Schmaus <f...@gentoo.org> writes:
> On 26/03/2023 22.30, Arsen Arsenović wrote: >> Closes: https://bugs.gentoo.org/902461 >> Signed-off-by: Arsen Arsenović <ar...@gentoo.org> >> --- >> eclass/toolchain-autoconf.eclass | 46 +++++++++++++++++++++++++++++--- >> 1 file changed, 43 insertions(+), 3 deletions(-) >> diff --git a/eclass/toolchain-autoconf.eclass >> b/eclass/toolchain-autoconf.eclass >> index 2ba27638468e..140ee4c9b5eb 100644 >> --- a/eclass/toolchain-autoconf.eclass >> +++ b/eclass/toolchain-autoconf.eclass >> @@ -1,4 +1,4 @@ >> -# Copyright 1999-2022 Gentoo Authors >> +# Copyright 1999-2023 Gentoo Authors >> # Distributed under the terms of the GNU General Public License v2 >> # @ECLASS: toolchain-autoconf.eclass >> @@ -18,6 +18,20 @@ esac >> if [[ -z ${_TOOLCHAIN_AUTOCONF_ECLASS} ]]; then >> _TOOLCHAIN_AUTOCONF_ECLASS=1 >> +# @ECLASS_VARIABLE: TC_AUTOCONF_BREAK_INFOS >> +# @DESCRIPTION: >> +# Enables slotting logic on the installed info pages. This includes >> +# mangling the pages in order to include a version number. Empty by >> +# default, and only exists for existing ebuild revisions to use. Set > > Referring to "existing ebuild revisions" becomes confusing in the future, when > there are existing ebuilds that do not use this variable. My intention was that this variable goes away as soon as said revisions are out of tree, so I wasn't thinking about that time-frame but I'll clarify and push to my branch. Thanks, have a lovely day. > Maybe "and only set by legacy ebuilds to phase out the broken slotting > logic. New ebuilds should not set this variable." > > - Flow -- Arsen Arsenović
signature.asc
Description: PGP signature