public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Matt Jolly <kangie@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH] rust.eclass: add ERUST_{SLOT,TYPE} user variables
Date: Wed, 4 Dec 2024 11:38:54 +1000	[thread overview]
Message-ID: <3a9b84bc-2cf0-40cf-abef-60f3d953892f@gentoo.org> (raw)
In-Reply-To: <2d6823930bf7b81f235f326d7a40482275ef7b6e.camel@gentoo.org>

Hi Michał,

Sure. No worries - Given the trivial nature I'll update the variable
before merging rather than sending a V2 unless there's other feedback
that requires it. :)

On 3/12/24 23:26, Michał Górny wrote:
> On Tue, 2024-12-03 at 22:22 +1000, kangie@gentoo.org wrote:
>> From: Matt Jolly <kangie@gentoo.org>
>>
>> These variables enable users (though most likely Gentoo developers)
>> to override the selection of the Rust implementation by the eclass.
>>
>> This means that _only_ the specified ERUST_SLOT and/or ERUST_TYPE
>> ('source' or 'binary') will be checked for, with the eclass `die`ing
>> with "No Rust slot satisfying the package's dependencies..." if the
>> selected impl is not available.
>>
>> These variables are intended to enable reproducing bugs and testing
>> packages against specific dev-lang/rust{,-bin} packages; they must
>> not be set in ebuilds.
>>
>> Closes: https://bugs.gentoo.org/945752
>> Signed-off-by: Matt Jolly <kangie@gentoo.org>
>> ---
>>   eclass/rust.eclass | 49 +++++++++++++++++++++++++++++++++++++++++-----
>>   1 file changed, 44 insertions(+), 5 deletions(-)
>>
>> diff --git a/eclass/rust.eclass b/eclass/rust.eclass
>> index 71cbb4b24f8c..991a9cdb7f14 100644
>> --- a/eclass/rust.eclass
>> +++ b/eclass/rust.eclass
>> @@ -98,6 +98,26 @@ declare -a -g -r _RUST_SLOTS_ORDERED=(
>>   	"1.54.0"
>>   )
>>   
>> +# == user control knobs ==
>> +
>> +# @ECLASS_VARIABLE: ERUST_SLOT
>> +# @USER_VARIABLE
>> +# @DESCRIPTION:
>> +# Specify the version (slot) of Rust to be used by the package. This is
>> +# useful for troubleshooting and debugging purposes; If unset, the newest
>> +# acceptable Rust version will be used. May be combined with ERUST_TYPE.
>> +# This variable must not be set in ebuilds.
>> +
>> +# @ECLASS_VARIABLE: ERUST_TYPE
>> +# @USER_VARIABLE
>> +# @DESCRIPTION:
>> +# Specify the type of Rust to be used by the package from options:
>> +# 'source' or 'binary' (-bin). This is useful for troubleshooting and
>> +# debugging purposes. If unset, the standard eclass logic will be used
>> +# to determine the type of Rust to use (i.e. prefer source if binary
>> +# is also available). May be combined with ERUST_SLOT.
>> +# This variable must not be set in ebuilds.
> 
> Could you perhaps add 'OVERRIDE' to the names, to make it clear they're
> not supposed to be normally used?  Just like we have
> PYTHON_COMPAT_OVERRIDE in Python eclasses.
> 



  reply	other threads:[~2024-12-04  1:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-03 12:22 [gentoo-dev] [PATCH] rust.eclass: add ERUST_{SLOT,TYPE} user variables kangie
2024-12-03 13:26 ` Michał Górny
2024-12-04  1:38   ` Matt Jolly [this message]
2024-12-04 17:45 ` Sam James

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=3a9b84bc-2cf0-40cf-abef-60f3d953892f@gentoo.org \
    --to=kangie@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