[MNT] installing task via make

[tschm]

We install task using a Makefile. For task please see https://taskfile.dev/

It's a lot more pleasant to work with task instead of make.

[tschm]

@fkiraly I am a big fan of task, see https://taskfile.dev/. Here we expose a make install-task. Task is like make on steroids.

[tschm]

Various other jobs will be added to the Makefile

[fkiraly]

Nice!

Could you kindly explain this to me like I am 5 year old, who would use the task framework under which circumstances?

Do we intend this to be purely developer facing?

[fkiraly]

Another note, also discussed in #658 - make is not operating system independent, so it will fail on some operating systems. We should ensure that the workflows we design work under a broad set of system conditions.

[tschm]

@fkiraly task is used by make and could also be used by the user directly. However, I tend to abstract it away by a layer of make above. I am aware make is not system independent but even the Windows users can make it happen. I think the best chance of using that kind of functionality.

[tschm]

task is also used at various places in the ci/cd framework without using make in between

[fkiraly]

If we want to use make, then imo only in the CI. We should not make make a required dependency in our basic user facing workflows, since it is not operating system independent.

It is true that, for instance, windows users can set it up, but it is behind a wall of complexity that we cannot assume users will get through just to run our code.

[tschm]

I have no problem to hit dem directly with uv and uvx. I see make as only one way into the project. There are other routes, e.g. task or directly from the command line with uv tools

[fkiraly]

hm, ok - but then we need to document all this.

(I think it is "going too deep" in the task/make layer, but if you would like this, I would not mind - as long as you document it for other devs)