Quote:
Originally Posted by encol
Thanks for sharing 
What differences/advantages has your approach compared to the others you mentioned? |
I am looking for the answer to that question myself.
If I reach my goal: "A ready to use plug-in appliance for Kindle Development", it will save other people a lot of time doing their own set-up.
So far, the only thing I needed to supply was the decision making involved in choosing what packages to include.
The SuSE (a.k.a: Novell, a.k.a: Micro Focus) Studio build system is almost a point-and-click system builder.
https://susestudio.com/appliance/create_new
The fun part will come with the addition of the ARM chroot and ARM cross-compile environments **inside** of the virtual machine.
Needless to say, they don't have that automated (or even thought of, far as I can tell).
But the system does have a way to run 'post build' scripts and to add-in overlays.
Which is probably how the Debian base stuff that matches the Kindle system versions will get laid in there (pun intended).