Questions and answers will be added when I recieve some :-)
I(Philippe De Swert) can be contacted at philippedeswert-at-scarlet.be
Q:Why is it called Stag and what does it stand for?
A:Stag is short for Stag beetle, and has not to be confounded with JTAG. It was choosen because the project needed a name. Because of the type of project it should be a small animal. The choice fell on this insect because it sports a sort of swiss knife, and it had a name which could be easily pronounced. It also points to my roots in scouting.(For the rest it is not yet an abbreviation, maybe ever...)
Q:Can Stag be used on other GNU/Linux distributions than Debian?.
A:Yes it can be used, but the functionality will be reduced. Apt is available on several other distro's. Which means that Debian packages can be installed on these distributions, however I don't think you will be able to build from source on those systems because they lack the debhelper tools en dpkg-(cross).
Q:Is it possible to use the Stag framework to build a mini-debian system?
A:Yes you can.(I do hope so if there are enough packages to do so in the future). However keep in mind that it is more aimed at tiny systems. By default it installs in a /var/rootfs-(arch) directory. However you can build a full system and tranfer the root-fs to another Pc or not embedded computer. Also a chrooted environment should be quite easy to build if you pretend to use your native compiler as a cross-compiler or the binary packages for your architecture.
Q:What about the EmDebian changes?
A:It was suggested (for this project and EmDebian's sake) that it was better to stay as compliant as possible with Debian. As such it would have been easy to add our changes to regular Debian packages. To keep it simple (and such spare work on the packagers so we can be able to persuade them to include the EmDebian way.) I created a new emdebian sub-dir used when building the package. Therefore I modified the dpkg-dev and debhelper tools.(Changes are not yet upstream).