@Shamar @TheGibson

In Clause 3.4 (in "Conditions"), what is the definition or "runtime"? I am thinking of the use case where you need to buy a proprietary compiler for a bare-bones processor. It is off-the-shelf but it is not an operating system (bare bones), and technically a compiler is not a runtime. Could you clarify this?

@Shamar @TheGibson

I'm sorry, that is still not clear enough. It hinges on the definition of "runtime", so I think that term should be defined or even expanded.

In the case of a bare-bones embedded system, what constitutes a "runtime"?

Usually a runtime is a set of libraries that come with the compiler. So it is in that sense part of the required off-the-shelf distribution, but usually one would call that a development kit, not an OS or runtime.

@Shamar @TheGibson

There is no catch.
If I understand it correctly, under your license it is OK that users have to pay for the OS or runtime but not for anything else. Is that correct?

@Shamar @TheGibson

OK, that is clear. I think it is reasonable because users nad hackers need an OS anyway, and you don't want to exclude those who use a proprietary OS. Maybe you could make this rationale a bit more explicit.

It just means that for some of my work I would not be able to use this license. That's OK, there are plenty of other suitable licenses.


Hi guys, I've updated the preamble and added a definitions of runtime to the .

Would you mind to give a look to the new version? tesio.it/documents/HACK.txt

In particular, @wim_v12e, I tried to clarify your doubts about the runtime in embedded systems: do you think the wording is better now?

I proposed it for discussion on Debian Legal, maybe you might find it interesting.

Please don't be shy to propose improvements.

Sign in to participate in the conversation

Server run by the main developers of the project 🐘 It is not focused on any particular niche interest - everyone is welcome as long as you follow our code of conduct!