-
Notifications
You must be signed in to change notification settings - Fork 8
Home
The first major goal is to support Raspbian 8.0 (jessie). And as far as that goes, A2SERVER itself probably already does that just fine. But A2SERVER is tied in with A2CLOUD which definitely does not, and other tools we use have been reported to have issues.
Next, we currently download most of our dependencies as pre-built binary tarball packages so that they need not be compiled on the rather puny CPU of the Raspberry Pi at installation time without need. The proper way to handle this (and to deal with our explicit dependencies) is to package everything for Debian. This isn't terribly difficult, it just needs to be done and the dependency graphs worked out.
Finally large portions of A2SERVER's installer are useful as standalone components if they can be improved and generalized. Making them into standalone tools is a longer-term project.
Ivan has provided a fair bit of information and notes he's used up until now. It ought to go here.