Preferably with a solution that fits the technological constraints.
Licensing in this project is rather fluid,
but everything in code/ is unconditionally under the following license:
This is released into the public domain.
No warranty is provided, implied or otherwise.
This will be referred to as "Public Domain".
It should be considered equivalent to CC0, and this is the intent,
but it is smaller, which is somewhat important when optimizing for size.
At this time, the majority of the code/ folder is by 20kdc, but exceptions may occur.
These exceptions must be documented below.
```
No exceptions exist at this time.
```
The repository folder is much more complex, as the structure represents places in a running system,
so licensing information cannot be directly bundled with the files that require it.
The contents of the repository/docs/licensing files represent a "full text" for a given license,
used in order to ensure legal compliance with a given license's "distribute with the program" clauses.
It is assumed that this is sufficient.
A user with access to a package requiring newer licensing information that does not update their licensing package is assumed to have made a willing choice.
If you find this assumption to be incorrect, please request the removal of the affected packages.
The limitations of OpenComputers affect the available choices here, and having separate license copies for each package is not an available choice.
Nor is having a separate license package for each individual license, unless you would prefer an unbrowsable repository.
The contents of the repository/docs/repo-authors file contains a full list of authorship and licensing information, per-file.
If you move a window over another window, that window has to rerender. The alternative is buffering the window. Since memory is a concern, that is not going to happen. Some windows are more expensive to render than others (`klogo` tries to use less RAM if the system is 192K, at the expense of disk access) - move the most expensive window out of the way, since once a window is top-most, moving it around is usually "free".
Secondly, for a compressed installer, you use `package.sh` to rebuild `code.tar` and `inst.lua`, which also prepares the final structure of the repository to upload.
The installer is split into a generic TAR extractor frontend `insthead.lua` and a replacable compression backend (written in by relevant tools - in current versions, `heroes.lua` is where it starts).
There was more details on this but the details changed.