Files
poky/meta/conf/distro/include/upstream_tracking.inc
Alexander Kanavin c19225ade4 upstream_tracking.inc: deprecate and move contents to recipes
No-update reasons and manual version checks should be in the recipes
themselves because otherwise they're prone to getting out of date.

(From OE-Core rev: b384345d9a693cbc3fd0dbeed9edd8c24618259d)

Signed-off-by: Alexander Kanavin <alexander.kanavin@linux.intel.com>
Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
2015-09-01 11:44:01 +01:00

25 lines
1.2 KiB
PHP

# NOTE: THIS FILE IS DEPRECATED. Please add new entries to the recipes themselves.
#
# upstream_tracking.inc - This file contains data that tracks the
# upstream project associated with a given recipe. This list is needed
# for recipes that version information can not be automagically discovered.
# As we automate this checking, this file will slowed be reduced.
#
# This data is used by the package reporting system (packages.yoctoproject.org)
#
# The format is as a bitbake variable override for each recipe
#
# RECIPE_UPSTREAM_VERSION_pn-<recipe name> = "<version>"
# RECIPE_UPSTREAM_DATE_pn-<recipe name> = "Mmm dd, YYYY"
# - This is the latest upstream version and date
# RECIPE_NO_UPDATE_REASON_pn-<recipe name> = "<free form text>"
# - Used to note why a recipe should not be upgraded to a newer versoin
# CHECK_DATE_pn-<recipe name> = "Mmm dd, YYYY"
# - This is the date that upstream was last manually checked over time
# this should be removed as we automate this checking
#
# These entries will slowly be removed as we can automatically determine
# the information in this file. So for existing recipes that we can get
# from the Recipe reporting system, the entries here can be removed.
#