5,705
edits
Changes
Jump to navigation
Jump to search
Line 22:
Line 22: − + − ** move packaging related code from glucose to 0sugar e.g. if there are two activity installations, one to /usr and one to ~/Activities, sugar decides what version is preferable, or what should happen if user removes activity. This is regular packaging work which should be moved to packaging system.+ − ** extensive usage of centralized (native packaging systems like rpm or deb) and decentralized (0install) models+ − ** patch 0install to support not read only usage of installed packages (some activities could be under development)+
→Long time tasks queue
* Improve [[Activity_Team/Polyol|Polyol]] libraries.
* Improve [[Activity_Team/Polyol|Polyol]] libraries.
* Encircle all packaging related stuff around sugar in one well designed packaging system - 0sugar:
* Encircle all packaging related stuff within sugar in one well designed packaging system, 0sugar:
# 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)
* ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar
* ActivityLibrary activity to replace existed shell (in case of managing activities) to support 0sugar