| 1 |
> On 28 Nov 2021, at 19:23, Zac Medico <zmedico@g.o> wrote: |
| 2 |
> |
| 3 |
>> [snip] |
| 4 |
> |
| 5 |
> How about if we also add a GO_DEPEND variable, so that eclasshi consumers can do something like BDEPEND="go? ( ${GO_DEPEND} )" ? |
| 6 |
> -- |
| 7 |
|
| 8 |
My preference is to go with what we've been doing more recently (do _OPTIONAL) so that |
| 9 |
consumers handle things properly and we don't have to try account for various cases |
| 10 |
(this was the problem with eclass variables which add a USE flag or depend only |
| 11 |
if a USE flag is set). |
| 12 |
|
| 13 |
But that said, I can't immediately think of any such annoying edge |
| 14 |
cases with this idea. It'd be additional to GO_OPTIONAL and it'd |
| 15 |
ensure a sane baseline Go version is chosen. So, why not? |
Archives