Misc notes after initial testing

[tchx84]

I tested it today, and these are a few notes and ideas I had while testing:

• Use actual machine names, e.g., rename "qemu" to "qemux86-64".
• Include machine name in base image YAML filename, e.g., derivative-base-image-{machine}.yml
• Include "git init" step in README, for kas to recognize the layer as a "repo".
• Include kas-container build example in README with the generated kas filename.

For the future:

• Exercise with meta-moonforge-rauc to see how to handle the mix of dynamic layers and kas fragments usage. This is a tricky use case, because kas doesn't support conditional inclusions, so the tool will need to know what "extra" kas fragment to add in those cases.
• Since this tools is already making it very easy, why not creating the full structure already. e.g., create "kas/include/repo/meta-moonforge.yml" instead and import it from the base image file? The reason for meta-derivative structure is that I wanted it to keep it simple to be easy to follow, but since this tool is doing magic we can try to impose the proper structure.

[ebassi]

Use actual machine names, e.g., rename "qemu" to "qemux86-64".

Sounds good, even though we really only support qemu for x86_64.

Include machine name in base image YAML filename, e.g., derivative-base-image-{machine}.yml

Sounds good.

Include "git init" step in README, for kas to recognize the layer as a "repo".

I think I want to add an option to initialise the directory with Git, similar to Cargo's --vcs=git option; this way I can also drop in a .gitignore that skips the build directory.

Include kas-container build example in README with the generated kas filename.

The documentation is definitely going to need a lot of work. :-)

I wonder if we should add kas as a dependency, so pip install moonforge-cli will automatically bring that in as well.

[ebassi]

@tchx84 PR #3 cleans up a couple of these issues.

[ebassi]

Since this tools is already making it very easy, why not creating the full structure already. e.g., create "kas/include/repo/meta-moonforge.yml" instead and import it from the base image file? The reason for meta-derivative structure is that I wanted it to keep it simple to be easy to follow, but since this tool is doing magic we can try to impose the proper structure.

This is fixed by #7