I appreciate that dependencies are always a concern for those developers working within the tighter constraints of an Embedded Platform.
However I'm afraid I don't agree that each platform should be able to choose each component individually and expect them to work with each other. Such flexibility is counter-productive, it slows the pace of development and ironically increases code size and thus makes each component itself less suitable for the embedded arena. If you find that D-Bus is too large for your requirements, what other systems have you been considering? Have you considered that the same time and effort might be better spent reducing the D-Bus resource usage? It should also be noted that Upstart itself has not been designed with memory thriftiness in mind, it's resource usage will be higher than other alternate init systems -- on the other hand, its integration and feature set will be much better. Scott -- Have you ever, ever felt like this? Had strange things happen? Are you going round the twist?
signature.asc
Description: This is a digitally signed message part
-- upstart-devel mailing list [email protected] Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/upstart-devel
