Instead of trying to get everything working at the same time with the new kernel and organising demos solely around that, the existing SL/RD system will be split approximately in half:
The Portable Half
- Package manager
- Graphics stack
- Some of the programming tools
These will probably be rebranded into a second package with other portable tools and used across different operating system kernels.
These may be packaged as a single unit or as a single unit with some extensions or some optional dependencies, but the individual tools will often work standalone on systems where other tools fail to build (i.e. you can ignore build failures except for the components you need).
The combined packaging idea is to simplify cyclic dependencies while the package manager & other tools are being developed, I don’t want everything neatly packaged in some totally unusable way! It may have custom installers so that it can be integrated with OS builds or this may come later/piece by piece.
The Kernel & Utilities
- Filesystem
- Kernel base
- C runtime
These will remain as the mostly-independent SL/RD kernel, but will probably gradually mix some code with other systems where sensible (e.g. possibly running SL/RD on top of an existing driver layer, or running an updated version of the filesystem across different kernels for further testing).
Flagship Packaging
The planned “flagship” SecureLang compiler range will probably initially be released under the CleanFork brand as an experimental OS extension.
This is partly because it may be handy earlier on with larger operating systems and partly because the development codename of the system SecureLang/Burrito naturally fits the CleanFork brand. This won’t run across the entire OS range as yet.
Leave a Reply