Platform Team/Infrastructure: Difference between revisions
mNo edit summary |
|||
| Line 1: | Line 1: | ||
Core issues that need to be fixed to accomplish the purpose: | |||
# Sugar projects dependencies. | |||
#* There is no decent way to treat activity dependencies for now. | |||
# Binary based Sugar projects. | |||
#* Existing scheme works fine only if Sugar projects are Python-based or intended to be launched only on a particular platform (or a particular version of a Sugar distribution). | |||
#* There is only one regular way to build development versions of Glucose projects - sugar-jhbuild, which is far less obvious than the activity development process, i.e., ''creating a sub-environment that includes glucose and all dependencies'' vs. ''checkout glucose project and run it''. | |||
# Convenient sharing of Sugar projects. | |||
#* Partially, complete? relates to sharing dependencies and binary based projects/dependencies issues. | |||
#* Excluding network-less environments, the only thing anyone should know about any Sugar project to run it from anywhere, is an unique Web url. | |||
=== Tools === | === Tools === | ||