summaryrefslogtreecommitdiffstats
path: root/meta/conf
diff options
context:
space:
mode:
authorRichard Purdie <richard.purdie@linuxfoundation.org>2018-12-17 22:57:32 +0000
committerRichard Purdie <richard.purdie@linuxfoundation.org>2018-12-18 16:19:34 +0000
commit42cc9e6c99f40a885352e17f7c7d68d70c3fffbd (patch)
treef69b3a8edda3384f5c8dcd0eaa93349d19999705 /meta/conf
parentb9c9018220cfc2d8e7591b3ced83952dd6ffe506 (diff)
downloadpoky-42cc9e6c99f40a885352e17f7c7d68d70c3fffbd.tar.gz
upstream-tracking.inc: Remove the long deprecated file
(From OE-Core rev: 22447eba250656489a6ed636fe58cb304d74e975) Signed-off-by: Richard Purdie <richard.purdie@linuxfoundation.org>
Diffstat (limited to 'meta/conf')
-rw-r--r--meta/conf/distro/include/upstream_tracking.inc24
1 files changed, 0 insertions, 24 deletions
diff --git a/meta/conf/distro/include/upstream_tracking.inc b/meta/conf/distro/include/upstream_tracking.inc
deleted file mode 100644
index e2a5e6ce40..0000000000
--- a/meta/conf/distro/include/upstream_tracking.inc
+++ /dev/null
@@ -1,24 +0,0 @@
1# NOTE: THIS FILE IS DEPRECATED. Please add new entries to the recipes themselves.
2#
3# upstream_tracking.inc - This file contains data that tracks the
4# upstream project associated with a given recipe. This list is needed
5# for recipes that version information can not be automagically discovered.
6# As we automate this checking, this file will slowed be reduced.
7#
8# This data is used by the package reporting system (packages.yoctoproject.org)
9#
10# The format is as a bitbake variable override for each recipe
11#
12# RECIPE_UPSTREAM_VERSION_pn-<recipe name> = "<version>"
13# RECIPE_UPSTREAM_DATE_pn-<recipe name> = "Mmm dd, YYYY"
14# - This is the latest upstream version and date
15# RECIPE_NO_UPDATE_REASON_pn-<recipe name> = "<free form text>"
16# - Used to note why a recipe should not be upgraded to a newer versoin
17# CHECK_DATE_pn-<recipe name> = "Mmm dd, YYYY"
18# - This is the date that upstream was last manually checked over time
19# this should be removed as we automate this checking
20#
21# These entries will slowly be removed as we can automatically determine
22# the information in this file. So for existing recipes that we can get
23# from the Recipe reporting system, the entries here can be removed.
24#