ToolingUseCases - Revision history

Eric: Undo revision 3281 by Yjytalamago (Talk)

2010-11-24T07:52:21Z

Undo revision 3281 by Yjytalamago (Talk)

← Older revision	Revision as of 07:52, 24 November 2010
(No difference)

2010-01-10T16:56:05Z

← Older revision		Revision as of 16:56, 10 January 2010
Line 78:		Line 78:
	** select images, packages, distros, machines, etc.		** select images, packages, distros, machines, etc.
	** have a simple 'installer' that does not require knowledge of bitbake/OE internals		** have a simple 'installer' that does not require knowledge of bitbake/OE internals

			[[Category:OEDEM]]

2010-01-10T16:33:06Z

remove categorization

← Older revision		Revision as of 16:33, 10 January 2010
Line 78:		Line 78:
	** select images, packages, distros, machines, etc.		** select images, packages, distros, machines, etc.
	** have a simple 'installer' that does not require knowledge of bitbake/OE internals		** have a simple 'installer' that does not require knowledge of bitbake/OE internals


	~~[[Category:DevTalk]]~~

2009-11-16T16:33:43Z

Package Developer

← Older revision		Revision as of 16:33, 16 November 2009
Line 51:		Line 51:
	* Debug build issues		* Debug build issues
	* Visualize Package Dependencies		* Visualize Package Dependencies

			=== Notes ===

			* OpenEmbedded Tools for Eclipse (OTE) was designed for this role type.

	== Target System User ==		== Target System User ==

2009-11-16T16:32:05Z

Target System User

← Older revision		Revision as of 16:32, 16 November 2009
Line 66:		Line 66:
	* find new packages and package updates for target		* find new packages and package updates for target
	* resolve package dependencies		* resolve package dependencies

			=== Ideas ===

			* A GUI application that runs with a local install of OE that can
			** present a wizard style interface that allows users to build system images
			** download overlays and other non-default artifacts
			** select images, packages, distros, machines, etc.
			** have a simple 'installer' that does not require knowledge of bitbake/OE internals


	[[Category:DevTalk]]		[[Category:DevTalk]]

2009-11-16T16:28:56Z

Ideas

← Older revision		Revision as of 16:28, 16 November 2009
Line 25:		Line 25:
	** For Java projects java-library based recipies are generated		** For Java projects java-library based recipies are generated
	** Python?		** Python?
			** Initially wizard can just create a tarball of project sources
			** Integration with SCM plugins?
			** How to capture project dependencies?
			** How to define export target? OTE, cloud, etc.?

	== Distro Developer ==		== Distro Developer ==

2009-11-16T16:25:46Z

Application Developer

← Older revision		Revision as of 16:25, 16 November 2009
Line 18:		Line 18:
	* Debug Application on Target		* Debug Application on Target
	* Generate build system artifacts for Application (recipes)		* Generate build system artifacts for Application (recipes)

			=== Ideas ===

			* Develop an Eclipse plugin to "Export project as Recipe"
			** For CDT (C/C++) projects make, automake recipes are generated
			** For Java projects java-library based recipies are generated
			** Python?

	== Distro Developer ==		== Distro Developer ==

2009-11-15T00:22:22Z

Target System User

← Older revision		Revision as of 00:22, 15 November 2009
Line 45:		Line 45:
	This role type typically is not exposed to package metadata, cross compilers, or build systems. They are system users, and as such, at times want to:		This role type typically is not exposed to package metadata, cross compilers, or build systems. They are system users, and as such, at times want to:

			* Generate system
	* Update system		* Update system
	* Install packages		* Install packages

2009-11-13T07:00:25Z

typo

← Older revision		Revision as of 07:00, 13 November 2009
Line 21:		Line 21:
	== Distro Developer ==		== Distro Developer ==

	Distro developer's concern is to compose packages and configurations into a working system. The ~~disto~~ developer has deep knowledge of packages available in Linux, and how sets of packages work well together. Additionally the distro developer is not afraid to work deeply within the build system to make it better, and to produce better, more maintainable package metadata and target systems.		Distro developer's concern is to compose packages and configurations into a working system. The distro developer has deep knowledge of packages available in Linux, and how sets of packages work well together. Additionally the distro developer is not afraid to work deeply within the build system to make it better, and to produce better, more maintainable package metadata and target systems.

	=== Primary Tooling Requirements ===		=== Primary Tooling Requirements ===

2009-11-11T18:52:03Z

Target System User

← Older revision		Revision as of 18:52, 11 November 2009
Line 48:		Line 48:
	* Install packages		* Install packages
	* Configure package metadata		* Configure package metadata

			=== Primary Tooling Requirements ===

			* install binary package on target
			* find new packages and package updates for target
			* resolve package dependencies

	[[Category:DevTalk]]		[[Category:DevTalk]]