public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Ionen Wolkens <ionen@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] cmake.eclass: Fix MYCMAKEARGS breakage with >=dev-util/cmake-3.23
Date: Wed, 16 Feb 2022 17:21:29 -0500	[thread overview]
Message-ID: <Yg146XT+zieiadLE@eversor> (raw)
In-Reply-To: <2181564.vFx2qVVIhK@tuxbrain>

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

On Wed, Feb 16, 2022 at 06:58:20PM +0100, Andreas Sturmlechner wrote:
> I'm not sure what this variable is about, but we gotta fix it.

Mentioned this in the bug too, but it's like MYMESONARGS and
EXTRA_ECONF. Not documented but it's still spread around by
word of mouth and sometime used by devs too when asking users
to try options ("does it work with MYCMAKEARGS=-DFIX emerge ...")

Any ebuilds using it directly (e.g. pcsx2) is a bug.

> ...and rather drop on next EAPI bump.

May result in some annoyed users that will ask for it back, not
that I think the use is that widespread unlike EXTRA_ECONF.

> -		"${MYCMAKEARGS}"
>  	)
>  
> +	if [[ -n ${MYCMAKEARGS} ]] ; then
> +		cmakeargs+=( "${MYCMAKEARGS}" )
> +	fi
> +

Better fix would've been to remove the quotes I think, so that it
splits arguments and doesn't pass a literal empty "" string.

i.e. users could MYCMAKEARGS="-DARG1=yes -DARG2=no" through package.env

-- 
ionen

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

  reply	other threads:[~2022-02-16 22:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-02-16 17:58 [gentoo-dev] [PATCH] cmake.eclass: Fix MYCMAKEARGS breakage with >=dev-util/cmake-3.23 Andreas Sturmlechner
2022-02-16 22:21 ` Ionen Wolkens [this message]
2022-02-16 22:27   ` Ionen Wolkens

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=Yg146XT+zieiadLE@eversor \
    --to=ionen@gentoo.org \
    --cc=gentoo-dev@lists.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