Activity Team/Obsolete/Native Packages - Revision history

Alsroot at 18:00, 25 November 2010

2010-11-25T18:00:04Z

← Older revision		Revision as of 14:00, 25 November 2010
Line 1:		Line 1:
			{{Obsolete \| It was only draft content}}

	<noinclude>{{TOCright}}		<noinclude>{{TOCright}}
	[[Category:Zero Sugar]]		[[Category:Zero Sugar]]

Alsroot: moved Activity Team/Zero Sugar/Native Packages to Activity Team/Obsolete/Native Packages

2010-11-25T17:58:44Z

moved Activity Team/Zero Sugar/Native Packages to Activity Team/Obsolete/Native Packages

← Older revision	Revision as of 13:58, 25 November 2010
(No difference)

FGrose at 16:17, 19 July 2010

2010-07-19T16:17:11Z

← Older revision		Revision as of 12:17, 19 July 2010
Line 1:		Line 1:
	{{TOCright}}		<noinclude>{{TOCright}}
	[[Category:Zero Sugar]]		[[Category:Zero Sugar]]
			</noinclude>
	== Summary ==		== Summary ==

	GNU/Linux distributions integration is not intended to follow all requirements ~~for~~ native packages and cannot be reused for distribution official repositories i.e. Zero Sugar is '''NOT''' a meta-packaging tool.		The GNU/Linux distributions integration feature of Zero Sugar is not intended to follow all the requirements of native packages and cannot be reused for distribution of official repositories, i.e., Zero Sugar is '''NOT''' a meta-packaging tool.

	There are only three major ideas behind distribution support:		There are only three major ideas behind native distribution support:
	* make packages, built on [http://build.opensuse.org/ OBS], reusable for 0install deployment model;		* make packages, built on [http://build.opensuse.org/ OBS], reusable for the 0install deployment model;
	* as a side effect, Zero packages could be installed on GNU/Linux distributions that OBS supports, also, Zero packages might be reused for OBS based Sugar distributions;		* as a side effect, Zero packages could be installed on GNU/Linux distributions that OBS supports, also, Zero packages might be reused for OBS-based Sugar distributions;
	* Zero Sugar does not support most of devil-in-details packaging features that make distro people's life so funny.		* Zero Sugar does not support most of the 'devil-in-details' packaging features that make distro people's life so funny.

	Each OBS package is generated by {{Code\|0sugar}} tool and might be built on a 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.		Each OBS package is generated by the {{Code\|0sugar}} tool, and might be built on a 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.

	<!--		<!--

Alsroot: /* Summary */

2010-07-19T13:11:38Z

Summary

← Older revision		Revision as of 09:11, 19 July 2010
Line 4:		Line 4:
	== Summary ==		== 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.		GNU/Linux distributions integration is not intended to follow all requirements for native packages and 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:		There are only three major ideas behind distribution support:
	* make packages, built on OBS, reusable for 0install deployment model;		* make packages, built on [http://build.opensuse.org/ OBS], reusable for 0install deployment model;
	* as a side effect, ~~run~~ Zero packages ~~in particular~~ GNU/Linux ~~distribution using~~ packages ~~built on~~ OBS ~~without interfering with official ones~~;		* as a side effect, Zero packages could be installed on GNU/Linux distributions that OBS supports, also, Zero packages might be reused for OBS based Sugar distributions;
	* support ~~OBS based Sugar distributions~~.		* Zero Sugar does not support most of devil-in-details packaging features that make distro people's life so funny.

	~~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.		Each OBS package is generated by {{Code\|0sugar}} tool and might be built on a 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.

	<!--		<!--

Alsroot: /* Summary */

2010-07-19T07:22:42Z

Summary

← Older revision		Revision as of 03:22, 19 July 2010
Line 8:		Line 8:
	There are only three major ideas behind distribution support:		There are only three major ideas behind distribution support:
	* make packages, built on OBS, reusable for 0install deployment model;		* 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~~;		* as a side effect, run Zero packages in particular GNU/Linux distribution using packages built on OBS without interfering with official ones;
	* support OBS based Sugar distributions.		* support OBS based Sugar distributions.

Alsroot at 07:21, 19 July 2010

2010-07-19T07:21:02Z

@@ Line 1: / Line 1: @@
-<noinclude>
+{{TOCright}}
-  {{TOCright}}
+[[Category:Zero Sugar]]
-  [[Category:Zero Sugar]]
-</noinclude>
+== Summary ==
 == 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
 ## 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
 -->

Alsroot: moved Activity Team/Zero Sugar/Implementation to Activity Team/Zero Sugar/Native Packages

2010-07-19T07:13:30Z

moved Activity Team/Zero Sugar/Implementation to Activity Team/Zero Sugar/Native Packages

← Older revision	Revision as of 03:13, 19 July 2010
(No difference)

Alsroot at 17:14, 3 July 2010

2010-07-03T17:14:43Z

← Older revision		Revision as of 13:14, 3 July 2010
Line 3:		Line 3:
	[[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 ==

Alsroot: /* GNU/Linux distributions */

2010-06-29T05:07:01Z

GNU/Linux distributions

← Older revision		Revision as of 01:07, 29 June 2010
Line 11:		Line 11:
	* make packages reusable for 0install deployment model		* make packages reusable for 0install deployment model

	Zero Sugar is designed to support primarily [http://build.opensuse.org/ OBS] workflow. Each OBS package is an all-sufficient Zero Sugar entity (with one exception, it knows nothing about 0install infrastructure~~) i~~.e. ~~it could be used as meta packaging tool (at least within~~ [http://wiki.opensuse.org/openSUSE:Build_Service_supported_build_targets distributions] that OBS supports~~). It is possible to follow regular OBS procedures for these~~ Zero ~~packages e.g. creating links to Zero packages and branching them within OBS~~.		Zero Sugar is designed to support primarily [http://build.opensuse.org/ OBS] workflow. Each OBS package is an all-sufficient Zero Sugar entity with one exception, it knows nothing about 0install infrastructure. It is possible to follow regular OBS procedures for Zero packages e.g. creating links and branching them.

			Within [http://wiki.opensuse.org/openSUSE:Build_Service_supported_build_targets distributions] that OBS supports, Zero Sugar could be considered as meta packaging tool.

	Each Zero package consist of:		Each Zero package consist of:

Alsroot: /* GNU/Linux distributions */

2010-06-29T05:00:18Z

GNU/Linux distributions

← Older revision		Revision as of 01:00, 29 June 2010
Line 6:		Line 6:
	== GNU/Linux distributions ==		== GNU/Linux distributions ==

	GNU/Linux distributions integration is not intended to follow all requirements for native packages and in most cases cannot be reused for ~~GNU/Linux~~ distribution official repositories. There are only three major ideas behind distribution support:		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. There are only three major ideas behind distribution support:
	* run Zero package in particular GNU/Linux distribution using native packaging system		* run Zero package in particular GNU/Linux distribution using native packaging system
	* do not interfere with official packages		* do not interfere with official packages
	* make packages reusable for 0install deployment model		* make packages reusable for 0install deployment model

	Zero Sugar ~~GNU/Linux distributions integration~~ is designed to support primarily [http://build.opensuse.org/ OBS] workflow. Each OBS package is an all-sufficient Zero Sugar entity with one exception, it knows nothing about 0install infrastructure. It is possible to follow regular OBS procedures for these Zero packages e.g. creating links to Zero packages and branching them within OBS.		Zero Sugar is designed to support primarily [http://build.opensuse.org/ OBS] workflow. Each OBS package is an all-sufficient Zero Sugar entity (with one exception, it knows nothing about 0install infrastructure) i.e. it could be used as meta packaging tool (at least within [http://wiki.opensuse.org/openSUSE:Build_Service_supported_build_targets distributions] that OBS supports). It is possible to follow regular OBS procedures for these Zero packages e.g. creating links to Zero packages and branching them within OBS.

	Each Zero package consist of:		Each Zero package consist of: