From: "Maxin B. John" <maxin.john@intel.com>
To: openembedded-core@lists.openembedded.org
Subject: [PATCH 1/4] package_regex.inc: remove deprecated file
Date: Thu, 19 May 2016 16:43:06 +0300 [thread overview]
Message-ID: <1463665389-18822-1-git-send-email-maxin.john@intel.com> (raw)
Remove this file as it has been deprecated in the previous release.
New entries should be added to recipes itself.
Signed-off-by: Maxin B. John <maxin.john@intel.com>
---
meta/classes/distrodata.bbclass | 1 -
meta/conf/distro/include/package_regex.inc | 22 ----------------------
2 files changed, 23 deletions(-)
delete mode 100644 meta/conf/distro/include/package_regex.inc
diff --git a/meta/classes/distrodata.bbclass b/meta/classes/distrodata.bbclass
index 51bfc1e..fbb7402 100644
--- a/meta/classes/distrodata.bbclass
+++ b/meta/classes/distrodata.bbclass
@@ -1,4 +1,3 @@
-include conf/distro/include/package_regex.inc
include conf/distro/include/upstream_tracking.inc
include conf/distro/include/distro_alias.inc
include conf/distro/include/maintainers.inc
diff --git a/meta/conf/distro/include/package_regex.inc b/meta/conf/distro/include/package_regex.inc
deleted file mode 100644
index 9fc1157..0000000
--- a/meta/conf/distro/include/package_regex.inc
+++ /dev/null
@@ -1,22 +0,0 @@
-# NOTE: THIS FILE IS DEPRECATED. Please add new entries to the recipes themselves.
-#
-# package_regex.inc - This file contains data that tracks
-# 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 slowly 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
-#"
-# UPSTREAM_CHECK_URI_pn-<recipe name> = "recipe_url"
-# - This is the url used by the package checking system to
-# get the latest version of the package
-# UPSTREAM_CHECK_REGEX_pn-<recipe name> = "package_regex"
-# - This is the regex the package checking system uses to
-# parse the page found at UPSTREAM_CHECK_URI_pn-<recipe name>
-# UPSTREAM_CHECK_GITTAGREGEX_pn-<recipe name> = "git_tag_regex"
-# - When source code is fetched from git, git tags are used to
-# determine the upstream release version. This regex can be used
-# to filter only relevant tags.
-#
--
2.4.0
next reply other threads:[~2016-05-19 13:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-05-19 13:43 Maxin B. John [this message]
2016-05-19 13:43 ` [PATCH 2/4] freetype: fix upstream check Maxin B. John
2016-05-19 13:43 ` [PATCH 3/4] libgudev: " Maxin B. John
2016-05-19 13:43 ` [PATCH 4/4] ghostscript: " Maxin B. John
2016-05-19 14:04 ` Burton, Ross
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1463665389-18822-1-git-send-email-maxin.john@intel.com \
--to=maxin.john@intel.com \
--cc=openembedded-core@lists.openembedded.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox