As we now got DJWillis and skeezix in the mailing list as well, I think we should start working on the OS for the Pyra as well, so that it will be developed at the same time as the hardware.
As mentioned, I'd like to use Debian (testing), as it has pretty good package management and is well-known. If someone prefers a different one, let me know :)
I'd like to stick to standard Debian as much as possible, so we've got as little work as possible as well.
Standard Debian is compiled without NEON optimization though, so I guess we should at least recompile most of the base packages we need.
As recompiling needs some CPU power, I was thinking of renting another small server which will only be used as build server for the OS.
I don't know exactly how things with Debian work, so please correct me if I'm wrong.
Our build server should...
* Grab selected package sources daily from Debian testing and recompile them with our parameters when they have been updated * Offer the compiled packages in a Debian Pyra-Repository (which has higher priority than the normal repository) * Offer additional packages specific for the Pyra (like libpnd, standard configuration, meta-package with all packages that are installed as default in our OS, our kernel, etc.) * Have all our own packages and stuff available in a GIT * Create files that can be used to fully reflash the OS using an SD Card (maybe once a week)
First step: Set up the basic build server and compile the packages. When that basic setup is working, we can think about what packages to include and build the meta-packages.
Is that the correct way to proceed?
DJWillis, do you think you can find some time to set this up? It seems there are some in the community who want to help as well (many discussions going on in the forums), but as we all know, that's not really reliable...
Maybe they can help with custom libraries and packages when the build server is working.
What do you all think?