Distro Tracking - Revision history

Eflanagan: /* More information for using the DISTRO_PN_ALIAS variable */

2015-04-16T12:37:24Z

More information for using the DISTRO_PN_ALIAS variable

← Older revision		Revision as of 12:37, 16 April 2015
Line 81:		Line 81:
	Note. You should have the following in your local.conf (or auto.conf):		Note. You should have the following in your local.conf (or auto.conf):

	include conf/distro/include/distro_alias.inc		include conf/distro/include/distro_alias.inc
	include conf/distro/include/recipe_color.inc		include conf/distro/include/recipe_color.inc
	include conf/distro/include/maintainers.inc		include conf/distro/include/maintainers.inc
	include conf/distro/include/upstream_tracking.inc		include conf/distro/include/upstream_tracking.inc
	include conf/distro/include/package_regex.inc		include conf/distro/include/package_regex.inc
	INHERIT+= "distrodata"		INHERIT+= "distrodata"

	The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.		The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.

Eflanagan: /* More information for using the DISTRO_PN_ALIAS variable */

2015-04-16T12:37:07Z

More information for using the DISTRO_PN_ALIAS variable

← Older revision		Revision as of 12:37, 16 April 2015
Line 75:		Line 75:

	For example, this command will generate a report, listing which linux distros include the		For example, this command will generate a report, listing which linux distros include the
	sources for each of the poky recipe ~~(note you need to have INHERIT += "distrodata" in your config)~~.		sources for each of the poky recipe.

	bitbake world -f -c distro_check		bitbake world -f -c distro_check

			Note. You should have the following in your local.conf (or auto.conf):

			include conf/distro/include/distro_alias.inc
			include conf/distro/include/recipe_color.inc
			include conf/distro/include/maintainers.inc
			include conf/distro/include/upstream_tracking.inc
			include conf/distro/include/package_regex.inc
			INHERIT+= "distrodata"

	The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.		The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.

Rpurdie: /* More information for using the DISTRO_PN_ALIAS variable */

2015-04-16T12:26:22Z

More information for using the DISTRO_PN_ALIAS variable

← Older revision		Revision as of 12:26, 16 April 2015
Line 75:		Line 75:

	For example, this command will generate a report, listing which linux distros include the		For example, this command will generate a report, listing which linux distros include the
	sources for each of the poky recipe.		sources for each of the poky recipe (note you need to have INHERIT += "distrodata" in your config).
	bitbake world -f -c distro_check		bitbake world -f -c distro_check
	~~This may require adding distrodata to the INHERIT list~~
	The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.		The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.

Meilei007: /* Package Tracking process */

2011-07-21T06:05:25Z

Package Tracking process

← Older revision		Revision as of 06:05, 21 July 2011
Line 10:		Line 10:
	The webpage can be found at http://packages.yoctoproject.org		The webpage can be found at http://packages.yoctoproject.org

	== Package Tracking ~~process~~ ==		== Package Tracking Process ==

	If we want to track the recipes latest status and do some upgrade work, below is the guideline.		If we want to track the recipes latest status and do some upgrade work, below is the guideline.
Line 30:		Line 30:

	When you decide not to upgrade one recipe, for the "git" type, please fill in the "RECIPE_NO_UPDATE_REASON " with first previous eight number, for other types, please fill in that field with the latest version you don't want to upgrade to. The report system will remove the recipe from the "need to upgrade packages" list if he detects the commit number or the latest version has existed in the "RECIPE_NO_UPDATE_REASON ".		When you decide not to upgrade one recipe, for the "git" type, please fill in the "RECIPE_NO_UPDATE_REASON " with first previous eight number, for other types, please fill in that field with the latest version you don't want to upgrade to. The report system will remove the recipe from the "need to upgrade packages" list if he detects the commit number or the latest version has existed in the "RECIPE_NO_UPDATE_REASON ".


	= Distro Tracking Fields =		= Distro Tracking Fields =

Meilei007 at 06:04, 21 July 2011

2011-07-21T06:04:36Z

← Older revision		Revision as of 06:04, 21 July 2011
Line 9:		Line 9:
	The Yocto Project hosts a package tracking website, that show information about the version and maintainership.		The Yocto Project hosts a package tracking website, that show information about the version and maintainership.
	The webpage can be found at http://packages.yoctoproject.org		The webpage can be found at http://packages.yoctoproject.org

			== Package Tracking process ==

			If we want to track the recipes latest status and do some upgrade work, below is the guideline.
			* Visit Packages Report System to get upgrade and manual check list.
			Visit http://packages.yoctoproject.org, check the Upgrade Packages List and Manual Check Packages List, find out how many recipes you need to upgrade or manual check.

			* Upgrade recipes
			Please refer to: Best Known Methods(BKMS) for Package Updating
			https://wiki.yoctoproject.org/wiki/Best_Known_Methods_(BKMs)_for_Package_Updating

			* Update distro_tracking_fields.inc
			For the explanation about fields in distro_tracking_fields.inc, please refer to https://wiki.yoctoproject.org/wiki/Distro_Tracking#Distro_Tracking_Fields

			There are two fields in the distro_tracking_fields.inc, one field is RECIPE_MANUAL_CHECK_DATE, and this is for those recipes which can't be checked upstream version automatically, if you checked the upstream version manually, please update it.

			Another field is RECIPE_LAST_UPDATE, this field record your last upgrade time, you need to update this field after you upgrade the recipe.

			It means that if you upgrade one recipe which on the Manual Check Packages List, you need to update those two fields at the same time.

			When you decide not to upgrade one recipe, for the "git" type, please fill in the "RECIPE_NO_UPDATE_REASON " with first previous eight number, for other types, please fill in that field with the latest version you don't want to upgrade to. The report system will remove the recipe from the "need to upgrade packages" list if he detects the commit number or the latest version has existed in the "RECIPE_NO_UPDATE_REASON ".

SaulWold at 22:46, 7 April 2011

2011-04-07T22:46:38Z

← Older revision		Revision as of 22:46, 7 April 2011
Line 21:		Line 21:
	;RECIPE_LATEST_VERSION		;RECIPE_LATEST_VERSION
	: The latest upstream stable version, "3.0"		: The latest upstream stable version, "3.0"
			;RECIPE_MANUAL_CHECK_DATE
			: This is the date of the last manual check for those packages that can not be checked automatically Date format is "Dec 10, 2010"
	;RECIPE_NO_UPDATE_REASON		;RECIPE_NO_UPDATE_REASON
	: An explaination as to why a recipe has not been updated to latest version, for example non stable or development version.		: An explaination as to why a recipe has not been updated to latest version, for example non stable or development version.
Line 37:		Line 39:
	;RECIPE_MAINTAINER		;RECIPE_MAINTAINER
	: Name and email address of the person maintaining the recipe, "Firstname Lastname <email.address>"		: Name and email address of the person maintaining the recipe, "Firstname Lastname <email.address>"

	~~Note that in the file, each field name is appended with -pn-<recipe name> as defined in [[#BitBake Overides\|BitBake Overrides]]~~

	;RECIPE_DISTRO_PN_ALIAS		;RECIPE_DISTRO_PN_ALIAS
	:		: See below for mre details

	==== More information for using the DISTRO_PN_ALIAS variable ====		==== More information for using the DISTRO_PN_ALIAS variable ====

SaulWold at 22:42, 7 April 2011

2011-04-07T22:42:04Z

← Older revision		Revision as of 22:42, 7 April 2011
Line 21:		Line 21:
	;RECIPE_LATEST_VERSION		;RECIPE_LATEST_VERSION
	: The latest upstream stable version, "3.0"		: The latest upstream stable version, "3.0"
			;RECIPE_NO_UPDATE_REASON
			: An explaination as to why a recipe has not been updated to latest version, for example non stable or development version.
	;RECIPE_NO_OF_PATCHES		;RECIPE_NO_OF_PATCHES
	: The number of patches we ship with the recipe.		: The number of patches we ship with the recipe.

SaulWold at 22:26, 7 April 2011

2011-04-07T22:26:11Z

← Older revision		Revision as of 22:26, 7 April 2011
Line 9:		Line 9:
	The Yocto Project hosts a package tracking website, that show information about the version and maintainership.		The Yocto Project hosts a package tracking website, that show information about the version and maintainership.
	The webpage can be found at http://packages.yoctoproject.org		The webpage can be found at http://packages.yoctoproject.org

	~~== Changing Maintainers ==~~

	~~From time to time recipe ownership changes, if you are interested in contributing to the Yocto Project~~
	~~recipes as part of OpenEmbedded-Core or other layers, then please take a look at the who the current maintainer~~
	~~is and let them know you would like to help. When you do that and the current owner replies, please update the~~
	~~distro_tracking_fields.inc with your name as RECIPE_MAINTAINER.~~

	~~=== Development Cycle & Updating ===~~

	~~As the Yocto Project wants to keep the to the most current stable release of the upstream projects, the~~
	~~maintainers will receive email during the development milestones reminding them to update their recipes~~
	~~as appropriate. This will also be tracked by the core maintainers, if a recipe is not updated in a timely~~
	~~manner, the core maintainers may update it directly. If the recipe maintainer is unable to continue updating~~
	~~their recipes beyond 1 release, the core maintainers may choose to re-assign the recipe, so the recipe does~~
	~~not become stale.~~

SaulWold: /* Distro Tracking Fields */

2011-04-07T20:40:43Z

Distro Tracking Fields

← Older revision		Revision as of 20:40, 7 April 2011
Line 29:		Line 29:
	= Distro Tracking Fields =		= Distro Tracking Fields =

	The file meta/conf/distro/include/distro_tracking_fields.inc exists to allow us to track various pieces of information about recipes and upstream versions (e.g, recipe maintainer contact information, date of latest upstream release, alternate names used for this recipe in other Linux distros, etc). We keep the metadata via [[#~~BitBake Overides~~\|BitBake Overrides]]. The following defines the meaning of each field:		The file meta/conf/distro/include/distro_tracking_fields.inc exists to allow us to track various pieces of information about recipes and upstream versions (e.g, recipe maintainer contact information, date of latest upstream release, alternate names used for this recipe in other Linux distros, etc). We keep the metadata via [[#BitBake_Overides\|BitBake Overrides]]. The following defines the meaning of each field:

	;RECIPE_STATUS		;RECIPE_STATUS

SaulWold at 20:22, 7 April 2011

2011-04-07T20:22:04Z

← Older revision		Revision as of 20:22, 7 April 2011
Line 27:		Line 27:


	== Distro Tracking Fields ==		= Distro Tracking Fields =

	The file meta/conf/distro/include/distro_tracking_fields.inc exists to allow us to track various pieces of information about recipes and upstream versions (e.g, recipe maintainer contact information, date of latest upstream release, alternate names used for this recipe in other Linux distros, etc). The following defines the meaning of each field:		The file meta/conf/distro/include/distro_tracking_fields.inc exists to allow us to track various pieces of information about recipes and upstream versions (e.g, recipe maintainer contact information, date of latest upstream release, alternate names used for this recipe in other Linux distros, etc). We keep the metadata via [[#BitBake Overides\|BitBake Overrides]]. The following defines the meaning of each field:

	;RECIPE_STATUS		;RECIPE_STATUS
Line 52:		Line 52:
	: Name and email address of the person maintaining the recipe, "Firstname Lastname <email.address>"		: Name and email address of the person maintaining the recipe, "Firstname Lastname <email.address>"

	Note that in the file, each field name is appended with -pn-<recipe name>.		Note that in the file, each field name is appended with -pn-<recipe name> as defined in [[#BitBake Overides\|BitBake Overrides]]
	~~= distro_tracking_fields.inc =~~

	* Recipe Status		;RECIPE_DISTRO_PN_ALIAS
	** Meets Recipe file Formating [[#Recipe File Rules\|rules]]		:
	** Use [[#BitBake Overides\|BitBake Overrides]] to track recipe status
	*** conf/distro/inc/recipe_status.inc
	*** RECIPE_STATUS_pn+<package_name>="<status_color>"
	*** where <status_color> is:
	**** Red: Major Needs Work
	**** Yellow: Some Work required
	**** Green: Clean (either already clean or easy to fix such that it's fixed during review)
	* Home Page
	* Bug Tracking Page
	* Check Dependencies completed (Check box column)
	** Ensure updated in Recipe file
	** Build time
	** Runtime
	** Use [[#BitBake Overides\|BitBake Overrides]] to indicate check is complete
	*** conf/distro/inc/dependency_check.inc
	*** DEPENCENCY_CHECK_pn+<package_name>="done"
	* Rate of Change Activity
	* Comments

	==== More information for using the DISTRO_PN_ALIAS variable ====		==== More information for using the DISTRO_PN_ALIAS variable ====
Line 91:		Line 72:
	sources for each of the poky recipe.		sources for each of the poky recipe.
	bitbake world -f -c distro_check		bitbake world -f -c distro_check
			This may require adding distrodata to the INHERIT list
	The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.		The results will be stored in the build/tmp/log/distro_check-${DATETIME}.results file.

	===== Other Distribution Package Search Tools =====		==== Other Distribution Package Search Tools ====

	~~(Thanks to Scott and Nitin for this list)~~

	;Debian		;Debian
Line 108:		Line 88:
	: http://www.rpmfind.net/linux/RPM/		: http://www.rpmfind.net/linux/RPM/

	==== BitBake Overrides ====		=== BitBake Overrides ===
	We will create a set of BitBake Overides for DEPENDENCY_CHECK and RECIPE_STATUS with defaults of "not done" and as recipes are checked the appropriate file will be updated to contain the status, these files will then be used to generate the spreadsheet / progress report so we know where we stand.		We will create a set of BitBake Overides for DEPENDENCY_CHECK and RECIPE_STATUS with defaults of "not done" and as recipes are checked the appropriate file will be updated to contain the status, these files will then be used to generate the spreadsheet / progress report so we know where we stand.