5,705
edits
Changes
Jump to navigation
Jump to search
Line 3:
Line 3: + + + + + + + + +
Activity Team/Obsolete/Native Packages (view source)
Revision as of 12:14, 3 July 2010
, 12:14, 3 July 2010no edit summary
[[Category:Zero Sugar]]
[[Category:Zero Sugar]]
</noinclude>
</noinclude>
== Levels ==
The entirely Zero Sugar infrastructure could be split into several levels:
# using spec file, build GNU/Linux distribution packages ([https://build.opensuse.org/ OBS] workflow is primarily supported) to let users install Zero packages from native packaging systems
# using spec file, generate [http://0install.net/ 0isntall] feeds to support [http://0install.net/goals.html#anyonedistrib fully decentralized] deployment model
# do not reinvent the wheel by implementing packaging related features in sugar. For example, for now, sugar manages what activities (i.e. packages) should be launched, from native packages in /usr or from ~/Activities, or sugar supports versioning scheme for activities (simple version numbers vs. dotted versions) or sugar supports MANIFEST files with not yet implemented hashes. All these are regular packaging procedures and it is already implemented. The idea is to reuse 0install as packaging "engine" keeping in mind that:
## its decentralized nature, sugar is all about (re)creating activities that should be some how distributed, using only distributors channels decrease sugar values
## it supports all existed GNU/Linux distribution efforts e.g. there is no need to repackage already packaged, by distros, software, 0install will use PackageKit to install it
== GNU/Linux distributions ==
== GNU/Linux distributions ==