Difference between revisions of "Activity Team/Obsolete/Native Packages"
< Activity Team | Obsolete
Jump to navigation
Jump to search
| Line 1: | Line 1: | ||
| − | + | {{TOCright}} | |
| − | + | [[Category:Zero Sugar]] | |
| − | + | ||
| − | < | + | == Summary == |
| + | |||
| + | GNU/Linux distributions integration is not intended to follow all requirements for native packages and in most cases cannot be reused for distribution official repositories i.e. Zero Sugar is '''NOT''' a meta-packaging tool. | ||
| + | |||
| + | There are only three major ideas behind distribution support: | ||
| + | * make packages, built on OBS, reusable for 0install deployment model; | ||
| + | * as a side effect, run Zero package in particular GNU/Linux distribution using native packaging system without interfering with official packages; | ||
| + | * support OBS based Sugar distributions. | ||
| + | |||
| + | Zero Sugar is designed to support primarily [http://build.opensuse.org/ OBS] workflow. Each OBS package is generated by {{Code|0sugar}} tool and might be built on bunch of rpm/deb based distributions within OBS. It is possible to follow regular OBS procedures for Zero packages e.g. creating links and branching them. | ||
| + | |||
| + | <!-- | ||
| + | === RPM support === | ||
| + | |||
| + | Each Zero package has ''rpm.spec'' file to support building package on all RPM based distributions that OBS supports. File contains only one line {{Code|%zsugar_spec}} to invoke {{Code|zsugar_spec}} macros which generates spec file content on demand according to current ''0sugar.info'' and ''revision'' files content. | ||
== Levels == | == Levels == | ||
| Line 12: | Line 26: | ||
## its decentralized nature, sugar is all about (re)creating activities that should be some how distributed, using only distributors channels decrease sugar values | ## 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 | ## 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 | ||
| − | + | --> | |
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 03:21, 19 July 2010
Summary
GNU/Linux distributions integration is not intended to follow all requirements for native packages and in most cases cannot be reused for distribution official repositories i.e. Zero Sugar is NOT a meta-packaging tool.
There are only three major ideas behind distribution support:
- make packages, built on OBS, reusable for 0install deployment model;
- as a side effect, run Zero package in particular GNU/Linux distribution using native packaging system without interfering with official packages;
- support OBS based Sugar distributions.
Zero Sugar is designed to support primarily OBS workflow. Each OBS package is generated by 0sugar tool and might be built on bunch of rpm/deb based distributions within OBS. It is possible to follow regular OBS procedures for Zero packages e.g. creating links and branching them.