User:Alsroot: Difference between revisions

Line 25:

# GNU/Linux distribution part, build activities and their dependencies on OBS using 0sugar.info spec file

# 0install part, compose 0isntall feeds using 0sugar.info spec file and use packages built on OBS as feeds implementations

# sugar part, collect all packaging related code in packaging core (could be dbus service) ~~i.e.~~ sugar shell will just ask packaging core to get list of all activities in the system (installed from native packages, via 0install, just placed to ~/Activities) or to launch particular activity by its id (packaging core will check what dependencies should be installed/downloaded and what sources to use, native packages or 0install)

# sugar part, collect all packaging related code in packaging core (could be dbus service)

## sugar shell will just ask packaging core to get list of all activities in the system (installed from native packages, via 0install, just placed to ~/Activities) or to launch particular activity by its id (packaging core will check what dependencies should be installed/downloaded and what sources to use, native packages or 0install)

## rainbow integration, having easy way to launch arbitrary blobs, security related issues are critical

* ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar

@@ Line 25: / Line 25: @@
 # GNU/Linux distribution part, build activities and their dependencies on OBS using 0sugar.info spec file
 # 0install part, compose 0isntall feeds using 0sugar.info spec file and use packages built on OBS as feeds implementations
-# sugar part, collect all packaging related code in packaging core (could be dbus service) i.e. sugar shell will just ask packaging core to get list of all activities in the system (installed from native packages, via 0install, just placed to ~/Activities) or to launch particular activity by its id (packaging core will check what dependencies should be installed/downloaded and what sources to use, native packages or 0install)
+# sugar part, collect all packaging related code in packaging core (could be dbus service)
+## sugar shell will just ask packaging core to get list of all activities in the system (installed from native packages, via 0install, just placed to ~/Activities) or to launch particular activity by its id (packaging core will check what dependencies should be installed/downloaded and what sources to use, native packages or 0install)
+## rainbow integration, having easy way to launch arbitrary blobs, security related issues are critical
 * ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar