More general mechanism for conditionally enabling recipes

[bluefing]

Attributes [Linux] , [Mac] etc are great but limited, for example while recent addition of [Android] is welcome, does it account for Termux vs Google's new Linux Terminal (i haven't checked yet)

My current use use case is developing in a devcontainer (Linux obviously) but on both Linux and Mac hosts.

i have recipes that are intended to be executed exclusively on the host or in the container (i use volume mount for source so justfile is in both)

Because I have the memory of a goldfish (which is why i love just) i manage this both by [group]ing and via a _ensure-host _ensure-container dependency.

The existing [Linux] [Mac] attributes are not sufficient to hide recipes because the host can vary depending on which machine I'm working on.

Can we consider adding e.g. [include(condition)] and perhaps [exclude(condition)] attributes to provide a more flexible mechanism - this would allow for checking if running in Termux, or running in a container?

Thanks

[casey]

There only needs to be one, and I think it would probably be called [enable]. There's already machinery to support expressions in [confirm] so this wouldn't be too hard.