USE flag array similar to USE_EXPAND

[NathanZachary]

Hello,

I'm working on an ebuild for the Ares multi-console video game emulator. Upstream allows for selecting the console support to build, and I would like to include that flexibility in the ebuild. As such, I was considering using something similar to the USE_EXPAND approach in the base profile, but specific to this package. I would appreciate some recommendations on how to handle it. For reference, here is the CMake option to pass to build only the console cores that one wants:

https://github.com/ares-emulator/ares/w ... ares_cores

Thank you in advance for the feedback.

Cheers,
Nathan Zachary

[RumpletonBongworth]

You could declare IUSE in this manner:

Code: Select all

IUSE="$(set -- ares_cores_{a26,fc,sfc,sg,ms,md,ps1,pce,ng,msx,cv,myvision,gb,gba,ws,ngp,spec,n64}; printf %s "$*")"

Effectively, this is a more convenient way of writing:

Code: Select all

IUSE="ares_cores_a26 ares_cores_fc ares_cores_sfc ares_cores_sg ares_cores_ms ares_cores_md ares_cores_ps1 ares_cores_pce ares_cores_ng ares_cores_msx ares_cores_cv ares_cores_myvision ares_cores_gb ares_cores_gba ares_cores_ws ares_cores_ngp ares_cores_spec ares_cores_n64"

As far as I am aware, there would be no way to whitelist ARES_CORES in USE_EXPAND without either creating a custom profile or getting your ebuild into the gentoo repo along with an agreement to modify the base profile accordingly. Nevertheless, whichever flags you choose to place into IUSE can always be enabled/disabled via package.use in their raw form. You might be better off just incorporating the flags without the "ares_cores_" prefix.

EDIT: Setting USE_EXPAND="ARES_CORES" in make.conf seems to work. That might be sufficient for personal use.