IMPROV: build dependencies

[gedw99]

for example the email example requires a build that include the email tag.

a dev has no way to know that ?
the cli does not tell them when that try to "build" down in the email examples folder ?

this is basically a capabilities issue. What does the main binary have, such that the script can rely on it being there if it needs it.

One way is simply to ask the binary what it has. Is there something on the CLI to tell me what the build tag was ? or even better a mapping of built tag to capabilities.

[refaktor]

The exact way how the modules are defined, built in and reported when missing is still yet to be done. We had one way of "most modules were off by default on Rye build", but people convinced me that at least at this stage, where there is not a system about it, better method is "on by default for most", so what I had in mind before changed a little. This will get on schedule.

[refaktor]

Hi, I want to look at this to move it forward, but most also the b_email module is now included by default. What example exactly were you testing?

In last few months most modules are included by default, but you can exclude them with build flags. We are moving toward a tool that parses module and retrieves information about it (see here https://ryelang.org/cookbook/improving-rye/one-source/), this also means that there will eventually be a global register of function names, so program in case a word is not defined will be able too look it up and ask if you are missing certain module (or any number of them).